Peaka
by ramamatarco.huggingface.ramamatar/peaka
- Remote endpoint
- 134 tools
Uptime
Checked · every day
99.64%from 4 days of checks
Up without downtime on 2 of 4 days with data; down 20 minutes in all, the longest 10 minutes on 31 October.
- No downtime
- Degraded
- Down over 5 minutes
- No data
- Not checked yet
Response time
Median 1254 ms, slowest 5% 1812 ms for the handshake and the tool list, over 30 days.
How far each check got
- Reached the address 75.0%
- Completed the handshake 50.0%
- Listed its tools 50.0%
134 tools at the last answer.
Every day
| Day | Result | Checks | Median |
|---|---|---|---|
| 3 Nov (today) | No downtime | 1 | 1812 ms |
| 2 Nov | Down 10 minutes | 3of 1 | 1254 ms |
| 1 Nov | No downtime | 1of 1 | 1310 ms |
| 31 Oct | Down 10 minutes | 3 | 1136 ms |
A failure counts as down time only when a second check five minutes later fails too. How we check
Connect to the publisher's own endpoint
Paste into Settings › Connectors › Add custom connector:
https://ramamatar-peaka.hf.space/gradio_api/mcp/sse Run in a terminal:
claude mcp add --transport sse peaka https://ramamatar-peaka.hf.space/gradio_api/mcp/sse Add to ~/.cursor/mcp.json:
Add to ~/.config/devin/mcp_config.json:
Add to mcp.json (Program › Install › Edit mcp.json):
Add to ~/.gemini/settings.json:
Add to config.json in oterm's data folder (~/Library/Application Support/oterm on macOS, ~/.local/share/oterm on Linux, %APPDATA%\oterm on Windows):
Add to ~/.config/eca/config.json (global) or .eca/config.json in the project:
{
"mcpServers": {
"peaka": {
"url": "https://ramamatar-peaka.hf.space/gradio_api/mcp/sse"
}
}
} Add to .vscode/mcp.json:
{
"servers": {
"peaka": {
"type": "sse",
"url": "https://ramamatar-peaka.hf.space/gradio_api/mcp/sse"
}
}
} Add to ~/.config/zed/settings.json:
{
"context_servers": {
"peaka": {
"url": "https://ramamatar-peaka.hf.space/gradio_api/mcp/sse"
}
}
} This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Add to cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers):
Add to anythingllm_mcp_servers.json in the AnythingLLM storage plugins directory:
Add to Augment Settings Panel – MCP section – Import from JSON (VS Code extension):
{
"mcpServers": {
"peaka": {
"type": "sse",
"url": "https://ramamatar-peaka.hf.space/gradio_api/mcp/sse"
}
}
} Add to ~/.continue/config.yaml:
mcpServers:
- name: "peaka"
type: sse
url: "https://ramamatar-peaka.hf.space/gradio_api/mcp/sse" Add to ~/.config/goose/config.yaml:
extensions:
"peaka":
type: streamable_http
name: "peaka"
enabled: true
uri: "https://ramamatar-peaka.hf.space/gradio_api/mcp/sse"
headers: {}
env_keys: []
envs: {}
timeout: 300 This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Run in a terminal:
codex mcp add peaka --url https://ramamatar-peaka.hf.space/gradio_api/mcp/sse This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Add to ~/.llm/config.json:
Add to resources/assets/config/mcp.json in the installed app:
Add to ~/.boltai/mcp.json:
Add to ~/.bob/settings/mcp.json (global) or .bob/mcp.json (project):
Add to ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace):
Add to ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace):
{
"mcpServers": {
"peaka": {
"url": "https://ramamatar-peaka.hf.space/gradio_api/mcp/sse"
}
}
} This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Add to ~/.config/agenvoy/mcp.json:
{
"servers": {
"peaka": {
"url": "https://ramamatar-peaka.hf.space/gradio_api/mcp/sse"
}
}
} This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Add to ~/.config/amp/settings.json (user) or .amp/settings.json (workspace):
{
"amp.mcpServers": {
"peaka": {
"url": "https://ramamatar-peaka.hf.space/gradio_api/mcp/sse"
}
}
} For agents: the install prompt
Every step above as one Markdown text, for an assistant installing it for you.
# Install the MCP server Peaka (`co.huggingface.ramamatar/peaka`)
Its page: https://plug.directory/servers/co.huggingface.ramamatar/peaka
It runs on the publisher's servers; the client connects to its URL.
Use the section for the person's client.
## Claude Desktop
Paste into Settings › Connectors › Add custom connector:
```text
https://ramamatar-peaka.hf.space/gradio_api/mcp/sse
```
## Claude Code
Run in a terminal:
```sh
claude mcp add --transport sse peaka https://ramamatar-peaka.hf.space/gradio_api/mcp/sse
```
## Cursor, Devin Desktop, LM Studio, Gemini CLI, oterm, ECA
Merge into the place for the person's client:
- Cursor: ~/.cursor/mcp.json
- Devin Desktop: ~/.config/devin/mcp_config.json
- LM Studio: mcp.json (Program › Install › Edit mcp.json)
- Gemini CLI: ~/.gemini/settings.json
- oterm: config.json in oterm's data folder (~/Library/Application Support/oterm on macOS, ~/.local/share/oterm on Linux, %APPDATA%\oterm on Windows)
- ECA: ~/.config/eca/config.json (global) or .eca/config.json in the project
```json
{
"mcpServers": {
"peaka": {
"url": "https://ramamatar-peaka.hf.space/gradio_api/mcp/sse"
}
}
}
```
## VS Code
Merge into .vscode/mcp.json:
```json
{
"servers": {
"peaka": {
"type": "sse",
"url": "https://ramamatar-peaka.hf.space/gradio_api/mcp/sse"
}
}
}
```
## Zed
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## Cline, AnythingLLM, Augment Code
Merge into the place for the person's client:
- Cline: cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers)
- AnythingLLM: anythingllm_mcp_servers.json in the AnythingLLM storage plugins directory
- Augment Code: Augment Settings Panel – MCP section – Import from JSON (VS Code extension)
```json
{
"mcpServers": {
"peaka": {
"type": "sse",
"url": "https://ramamatar-peaka.hf.space/gradio_api/mcp/sse"
}
}
}
```
## Continue
Merge into ~/.continue/config.yaml:
```yaml
mcpServers:
- name: "peaka"
type: sse
url: "https://ramamatar-peaka.hf.space/gradio_api/mcp/sse"
```
## Goose
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## Codex
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## mcp-client-cli, TUUI, BoltAI, Bob Shell, Kiro, Kiro CLI
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## Agenvoy
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## Amp
Merge into ~/.config/amp/settings.json (user) or .amp/settings.json (workspace):
```json
{
"amp.mcpServers": {
"peaka": {
"url": "https://ramamatar-peaka.hf.space/gradio_api/mcp/sse"
}
}
}
```
Then restart the client, or reload its MCP servers, and ask it to list the server's tools to confirm it started.
Tools 134
peaka_delete__ai_agent_projectId_threads_threadIdDelete ai-agent threadpeaka_delete__connections_projectId_connectionIdDeletes the specified Connection. Any catalogs using this connection will lose access to their data source.peaka_delete__data_projects_projectId_bitable_tableNamePermanently deletes the specified [Peaka BI Table](https://docs.peaka.com/connecting-your-data/peaka-bi-table) and all its data from the project. This action is irreversible — all rows, columns, and schema definitions associated with the BI Table will be removed.peaka_delete__data_projects_projectId_bitable_tableName_columns_columnNamePermanently removes a column from the specified [Peaka BI Table](https://docs.peaka.com/connecting-your-data/peaka-bi-table). This action is irreversible — the column and all its stored data will be deleted from the BI Table.peaka_delete__data_projects_projectId_cache_cacheIdPermanently deletes a cache and all its associated data. This operation: - Cancels any running or scheduled sync workflows (both incremental and full refresh). - Drops the cached table from the internal BigTable store. - Removes all cache settings, execution history, and status records. This action is irreversible. To re-cache the table, a new cache must be created from scratch.peaka_delete__data_projects_projectId_catalogs_catalogIdPermanently removes the specified catalog from the project. This disconnects the underlying data source and makes all its schemas and tables unavailable for querying. This action is irreversible.peaka_delete__data_projects_projectId_catalogs_catalogId_parametricTablesDeletes a Parametric Table identified by its target schema and table name. The original source table is not affected.peaka_delete__data_projects_projectId_exports_exportIdCancels a PENDING/RUNNING export (kills the running query and cleans up partial artifacts). A no-op on an already-finished job. Idempotent.peaka_delete__data_projects_projectId_queries_folders_folderIdDeletes a query folder by its ID. By default, only empty folders can be deleted. Set force=true to recursively delete the folder along with all its sub-folders and contained queries.peaka_delete__data_projects_projectId_queries_queryIdPermanently deletes a query by its ID.peaka_delete__data_projects_projectId_semantic_catalogs_catalogId_table_tableIdDeletes the specified Semantic Table from a Semantic Catalog.peaka_delete__data_projects_projectId_table_tableNamePermanently deletes the specified [Peaka Table](https://docs.peaka.com/connecting-your-data/peaka-table) and all its data from the project. This action is irreversible — all rows, columns, and schema definitions associated with the table will be removed.
From Hugging Face Spaces. Report a problem