Elijahdev0 MCP

MCP运维云端

提供方 elijahdev0

运维云端 未标注 无需鉴权 社区 / 第三方 Claude

提供Model Context Protocol (MCP)接口的服务器,用于管理和调用工具、代理、数据源等资源。

一句话选型结论

按资料字段整理

Elijahdev0 MCP 属于运维云端类 MCP 服务器,传输方式未标注,无需鉴权,可直接接入 Claude,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类运维云端 传输方式未标注 鉴权无需鉴权 部署方式未标注
GitHub 星标 0 仓库热度,无公开仓库时显示未标注
工具数 120 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

运维云端
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量120暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

API接口JavaScript本地部署工具管理代理管理数据源管理

安装与配置

未标注 无需鉴权
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后客户端会列出约 120 个工具,随便调一个只读工具确认能返回结果。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
云资源查询

查实例、存储、账单等云上资源状态。

部署与发布

把部署、重启、回滚这类操作接进对话。

监控与告警

拉取监控指标,异常时让模型帮你判断。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 资料标注 120 个工具,覆盖面较广,能满足多种调用。
  • 已适配 Claude,换客户端不用重新研究配置。
  • 资料标注无需鉴权,装好就能连。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在运维云端场景里让模型直接调用外部能力的人。
  • 已经在用 Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Elijahdev0 MCP当前 120 未标注 未标注 无 2026-05-17
lobehub 未标注 stdio · 本地进程 本地部署 有 2026-04-11
TrendRadar 未标注 stdio · 本地进程 本地部署 有 2026-04-13
Ui Tars Desktop 8a825770 未标注 stdio · 本地进程 本地部署 有 2026-05-17
ruflo 未标注 stdio · 本地进程 本地部署 有 2026-04-13
FastGPT 未标注 stdio · 本地进程 本地部署 有 2026-04-11

服务器档案

运维云端
字段来自项目仓库与公开索引,中文说明由本站标注
提供方elijahdev0上游标注的维护方 elijahdev0
分类运维云端本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式无需鉴权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

42.3 KB
来自项目仓库与上游目录的原文,未做删改

openapi-mcp-server

Model Context Protocol (MCP) server for Letta API.

Description

This server provides a Model Context Protocol (MCP) interface to the API.

Installation

  1. Install dependencies:```bash
    npm install

2. Create a `.env` file based on `.env.example`:```bash
cp .env.example .env
  1. Edit the .env file to add your API configuration and authorization details.

Configuration

The following environment variables can be configured in the .env file:

  • API_BASE_URL: Base URL for the API (required)
  • SERVER_NAME: Name of the MCP server (default: "openapi-mcp-server")
  • SERVER_VERSION: Version of the MCP server (default: "1.0.0")
  • DEBUG: Enable debug logging (true/false) (default: false)

Usage

Running the Server

The server is provided as both JavaScript and TypeScript versions:```bash

Run JavaScript version

npm start

Or run TypeScript version (compiles on the fly)

npm run start:ts


### Building the TypeScript Version```bash
npm run build
cd dist
node server.js

Using as an MCP Tool Provider

This server implements the Model Context Protocol (MCP) and can be used with any MCP-compatible consumer, like Claude.js client or other MCP consumers.

Example of connecting to this server from a Claude.js client:```javascript
import { MCP } from "claude-js";
import { createStdio } from "claude-js/mcp";

// Create stdin/stdout transport
const transport = createStdio({ command: "node path/to/server.js" });

// Connect to the MCP server
const mcp = new MCP({ transport });
await mcp.connect();

// List available tools
const { tools } = await mcp.listTools();
console.log("Available tools:", tools);

// Call a tool
const result = await mcp.callTool({
id: "TOOL-ID",
arguments: { param1: "value1" }
});
console.log("Tool result:", result);
```

Available Tools

This MCP server provides the following tools:

delete_tool

  • ID: DELETE-v1-tools-tool-id
  • Description: Delete a tool by name
  • Method: DELETE
  • Path: /v1/tools/{tool_id}

Parameters:

  • tool_id: tool_id parameter (required)
  • user_id: user_id parameter

retrieve_tool

  • ID: GET-v1-tools-tool-id
  • Description: Get a tool by ID
  • Method: GET
  • Path: /v1/tools/{tool_id}

Parameters:

  • tool_id: tool_id parameter (required)
  • user_id: user_id parameter

modify_tool

  • ID: PATCH-v1-tools-tool-id
  • Description: Update an existing tool
  • Method: PATCH
  • Path: /v1/tools/{tool_id}

Parameters:

  • tool_id: tool_id parameter (required)
  • user_id: user_id parameter

list_tools

  • ID: GET-v1-tools-
  • Description: Get a list of all tools available to agents belonging to the org of the user
  • Method: GET
  • Path: /v1/tools/

Parameters:

  • after: after parameter
  • limit: limit parameter
  • name: name parameter
  • user_id: user_id parameter

create_tool

  • ID: POST-v1-tools-
  • Description: Create a new tool
  • Method: POST
  • Path: /v1/tools/

Parameters:

  • user_id: user_id parameter

upsert_tool

  • ID: PUT-v1-tools-
  • Description: Create or update a tool
  • Method: PUT
  • Path: /v1/tools/

Parameters:

  • user_id: user_id parameter

add_base_tools

  • ID: POST-v1-tools-add-base-tools
  • Description: Upsert base tools
  • Method: POST
  • Path: /v1/tools/add-base-tools

Parameters:

  • user_id: user_id parameter

run_tool_from_source

  • ID: POST-v1-tools-run
  • Description: Attempt to build a tool from source, then run it on the provided arguments
  • Method: POST
  • Path: /v1/tools/run

Parameters:

  • user_id: user_id parameter

list_composio_apps

  • ID: GET-v1-tools-composio-apps
  • Description: Get a list of all Composio apps
  • Method: GET
  • Path: /v1/tools/composio/apps

Parameters:

  • user-id: user-id parameter

list_composio_actions_by_app

  • ID: GET-v1-tools-composio-apps-composio-app-name-actions
  • Description: Get a list of all Composio actions for a specific app
  • Method: GET
  • Path: /v1/tools/composio/apps/{composio_app_name}/actions

Parameters:

  • composio_app_name: composio_app_name parameter (required)
  • user_id: user_id parameter

add_composio_tool

  • ID: POST-v1-tools-composio-composio-action-name
  • Description: Add a new Composio tool by action name (Composio refers to each tool as an Action)
  • Method: POST
  • Path: /v1/tools/composio/{composio_action_name}

Parameters:

  • composio_action_name: composio_action_name parameter (required)
  • user_id: user_id parameter

list_mcp_servers

  • ID: GET-v1-tools-mcp-servers
  • Description: Get a list of all configured MCP servers
  • Method: GET
  • Path: /v1/tools/mcp/servers

Parameters:

  • user-id: user-id parameter

add_mcp_server

  • ID: PUT-v1-tools-mcp-servers
  • Description: Add a new MCP server to the Letta MCP server config
  • Method: PUT
  • Path: /v1/tools/mcp/servers

Parameters:

  • user_id: user_id parameter

list_mcp_tools_by_server

  • ID: GET-v1-tools-mcp-servers-mcp-server-name-tools
  • Description: Get a list of all tools for a specific MCP server
  • Method: GET
  • Path: /v1/tools/mcp/servers/{mcp_server_name}/tools

Parameters:

  • mcp_server_name: mcp_server_name parameter (required)
  • user_id: user_id parameter

add_mcp_tool

  • ID: POST-v1-tools-mcp-servers-mcp-server-name-mcp-tool-name
  • Description: Register a new MCP tool as a Letta server by MCP server + tool name
  • Method: POST
  • Path: /v1/tools/mcp/servers/{mcp_server_name}/{mcp_tool_name}

Parameters:

  • mcp_server_name: mcp_server_name parameter (required)
  • mcp_tool_name: mcp_tool_name parameter (required)
  • user_id: user_id parameter

delete_mcp_server

  • ID: DELETE-v1-tools-mcp-servers-mcp-server-name
  • Description: Add a new MCP server to the Letta MCP server config
  • Method: DELETE
  • Path: /v1/tools/mcp/servers/{mcp_server_name}

Parameters:

  • mcp_server_name: mcp_server_name parameter (required)
  • user_id: user_id parameter

retrieve_source

  • ID: GET-v1-sources-source-id
  • Description: Get all sources
  • Method: GET
  • Path: /v1/sources/{source_id}

Parameters:

  • source_id: source_id parameter (required)
  • user_id: user_id parameter

modify_source

  • ID: PATCH-v1-sources-source-id
  • Description: Update the name or documentation of an existing data source.
  • Method: PATCH
  • Path: /v1/sources/{source_id}

Parameters:

  • source_id: source_id parameter (required)
  • user_id: user_id parameter

delete_source

  • ID: DELETE-v1-sources-source-id
  • Description: Delete a data source.
  • Method: DELETE
  • Path: /v1/sources/{source_id}

Parameters:

  • source_id: source_id parameter (required)
  • user_id: user_id parameter

get_source_id_by_name

  • ID: GET-v1-sources-name-source-name
  • Description: Get a source by name
  • Method: GET
  • Path: /v1/sources/name/{source_name}

Parameters:

  • source_name: source_name parameter (required)
  • user_id: user_id parameter

list_sources

  • ID: GET-v1-sources-
  • Description: List all data sources created by a user.
  • Method: GET
  • Path: /v1/sources/

Parameters:

  • user_id: user_id parameter

create_source

  • ID: POST-v1-sources-
  • Description: Create a new data source.
  • Method: POST
  • Path: /v1/sources/

Parameters:

  • user_id: user_id parameter

upload_file_to_source

  • ID: POST-v1-sources-source-id-upload
  • Description: Upload a file to a data source.
  • Method: POST
  • Path: /v1/sources/{source_id}/upload

Parameters:

  • source_id: source_id parameter (required)
  • user_id: user_id parameter

list_source_passages

  • ID: GET-v1-sources-source-id-passages
  • Description: List all passages associated with a data source.
  • Method: GET
  • Path: /v1/sources/{source_id}/passages

Parameters:

  • source_id: source_id parameter (required)
  • user_id: user_id parameter

list_source_files

  • ID: GET-v1-sources-source-id-files
  • Description: List paginated files associated with a data source.
  • Method: GET
  • Path: /v1/sources/{source_id}/files

Parameters:

  • source_id: source_id parameter (required)
  • limit: Number of files to return
  • after: Pagination cursor to fetch the next set of results
  • user_id: user_id parameter

delete_file_from_source

  • ID: DELETE-v1-sources-source-id-file-id
  • Description: Delete a data source.
  • Method: DELETE
  • Path: /v1/sources/{source_id}/{file_id}

Parameters:

  • source_id: source_id parameter (required)
  • file_id: file_id parameter (required)
  • user_id: user_id parameter

list_agents

  • ID: GET-v1-agents-
  • Description: List all agents associated with a given user.

This endpoint retrieves a list of all agents and their configurations
associated with the specified user ID.
- Method: GET
- Path: /v1/agents/

Parameters:

  • name: Name of the agent
  • tags: List of tags to filter agents by
  • match_all_tags: If True, only returns agents that match ALL given tags. Otherwise, return agents that have ANY of the passed-in tags.
  • before: Cursor for pagination
  • after: Cursor for pagination
  • limit: Limit for pagination
  • query_text: Search agents by name
  • project_id: Search agents by project ID
  • template_id: Search agents by template ID
  • base_template_id: Search agents by base template ID
  • identity_id: Search agents by identity ID
  • identifier_keys: Search agents by identifier keys
  • include_relationships: Specify which relational fields (e.g., 'tools', 'sources', 'memory') to include in the response. If not provided, all relationships are loaded by default. Using this can optimize performance by reducing unnecessary joins.
  • ascending: Whether to sort agents oldest to newest (True) or newest to oldest (False, default)
  • user_id: user_id parameter

create_agent

  • ID: POST-v1-agents-
  • Description: Create a new agent with the specified configuration.
  • Method: POST
  • Path: /v1/agents/

Parameters:

  • user_id: user_id parameter
  • X-Project: X-Project parameter

export_agent_serialized

  • ID: GET-v1-agents-agent-id-export
  • Description: Export the serialized JSON representation of an agent.
  • Method: GET
  • Path: /v1/agents/{agent_id}/export

Parameters:

  • agent_id: agent_id parameter (required)
  • user_id: user_id parameter

import_agent_serialized

  • ID: POST-v1-agents-import
  • Description: Import a serialized agent file and recreate the agent in the system.
  • Method: POST
  • Path: /v1/agents/import

Parameters:

  • append_copy_suffix: If set to True, appends "_copy" to the end of the agent name.
  • override_existing_tools: If set to True, existing tools can get their source code overwritten by the uploaded tool definitions. Note that Letta core tools can never be updated externally.
  • project_id: The project ID to associate the uploaded agent with.
  • user_id: user_id parameter

retrieve_agent_context_window

  • ID: GET-v1-agents-agent-id-context
  • Description: Retrieve the context window of a specific agent.
  • Method: GET
  • Path: /v1/agents/{agent_id}/context

Parameters:

  • agent_id: agent_id parameter (required)
  • user_id: user_id parameter

modify_agent

  • ID: PATCH-v1-agents-agent-id
  • Description: Update an existing agent
  • Method: PATCH
  • Path: /v1/agents/{agent_id}

Parameters:

  • agent_id: agent_id parameter (required)
  • user_id: user_id parameter

retrieve_agent

  • ID: GET-v1-agents-agent-id
  • Description: Get the state of the agent.
  • Method: GET
  • Path: /v1/agents/{agent_id}

Parameters:

  • agent_id: agent_id parameter (required)
  • user_id: user_id parameter

delete_agent

  • ID: DELETE-v1-agents-agent-id
  • Description: Delete an agent.
  • Method: DELETE
  • Path: /v1/agents/{agent_id}

Parameters:

  • agent_id: agent_id parameter (required)
  • user_id: user_id parameter

list_agent_tools

  • ID: GET-v1-agents-agent-id-tools
  • Description: Get tools from an existing agent
  • Method: GET
  • Path: /v1/agents/{agent_id}/tools

Parameters:

  • agent_id: agent_id parameter (required)
  • user_id: user_id parameter

attach_tool

  • ID: PATCH-v1-agents-agent-id-tools-attach-tool-id
  • Description: Attach a tool to an agent.
  • Method: PATCH
  • Path: /v1/agents/{agent_id}/tools/attach/{tool_id}

Parameters:

  • agent_id: agent_id parameter (required)
  • tool_id: tool_id parameter (required)
  • user_id: user_id parameter

detach_tool

  • ID: PATCH-v1-agents-agent-id-tools-detach-tool-id
  • Description: Detach a tool from an agent.
  • Method: PATCH
  • Path: /v1/agents/{agent_id}/tools/detach/{tool_id}

Parameters:

  • agent_id: agent_id parameter (required)
  • tool_id: tool_id parameter (required)
  • user_id: user_id parameter

attach_source_to_agent

  • ID: PATCH-v1-agents-agent-id-sources-attach-source-id
  • Description: Attach a source to an agent.
  • Method: PATCH
  • Path: /v1/agents/{agent_id}/sources/attach/{source_id}

Parameters:

  • agent_id: agent_id parameter (required)
  • source_id: source_id parameter (required)
  • user_id: user_id parameter

detach_source_from_agent

  • ID: PATCH-v1-agents-agent-id-sources-detach-source-id
  • Description: Detach a source from an agent.
  • Method: PATCH
  • Path: /v1/agents/{agent_id}/sources/detach/{source_id}

Parameters:

  • agent_id: agent_id parameter (required)
  • source_id: source_id parameter (required)
  • user_id: user_id parameter

list_agent_sources

  • ID: GET-v1-agents-agent-id-sources
  • Description: Get the sources associated with an agent.
  • Method: GET
  • Path: /v1/agents/{agent_id}/sources

Parameters:

  • agent_id: agent_id parameter (required)
  • user_id: user_id parameter

retrieve_agent_memory

  • ID: GET-v1-agents-agent-id-core-memory
  • Description: Retrieve the memory state of a specific agent.
    This endpoint fetches the current memory state of the agent identified by the user ID and agent ID.
  • Method: GET
  • Path: /v1/agents/{agent_id}/core-memory

Parameters:

  • agent_id: agent_id parameter (required)
  • user_id: user_id parameter

retrieve_core_memory_block

  • ID: GET-v1-agents-agent-id-core-memory-blocks-block-label
  • Description: Retrieve a core memory block from an agent.
  • Method: GET
  • Path: /v1/agents/{agent_id}/core-memory/blocks/{block_label}

Parameters:

  • agent_id: agent_id parameter (required)
  • block_label: block_label parameter (required)
  • user_id: user_id parameter

modify_core_memory_block

  • ID: PATCH-v1-agents-agent-id-core-memory-blocks-block-label
  • Description: Updates a core memory block of an agent.
  • Method: PATCH
  • Path: /v1/agents/{agent_id}/core-memory/blocks/{block_label}

Parameters:

  • agent_id: agent_id parameter (required)
  • block_label: block_label parameter (required)
  • user_id: user_id parameter

list_core_memory_blocks

  • ID: GET-v1-agents-agent-id-core-memory-blocks
  • Description: Retrieve the core memory blocks of a specific agent.
  • Method: GET
  • Path: /v1/agents/{agent_id}/core-memory/blocks

Parameters:

  • agent_id: agent_id parameter (required)
  • user_id: user_id parameter

attach_core_memory_block

  • ID: PATCH-v1-agents-agent-id-core-memory-blocks-attach-block-id
  • Description: Attach a core memoryblock to an agent.
  • Method: PATCH
  • Path: /v1/agents/{agent_id}/core-memory/blocks/attach/{block_id}

Parameters:

  • agent_id: agent_id parameter (required)
  • block_id: block_id parameter (required)
  • user_id: user_id parameter

detach_core_memory_block

  • ID: PATCH-v1-agents-agent-id-core-memory-blocks-detach-block-id
  • Description: Detach a core memory block from an agent.
  • Method: PATCH
  • Path: /v1/agents/{agent_id}/core-memory/blocks/detach/{block_id}

Parameters:

  • agent_id: agent_id parameter (required)
  • block_id: block_id parameter (required)
  • user_id: user_id parameter

list_passages

  • ID: GET-v1-agents-agent-id-archival-memory
  • Description: Retrieve the memories in an agent's archival memory store (paginated query).
  • Method: GET
  • Path: /v1/agents/{agent_id}/archival-memory

Parameters:

  • agent_id: agent_id parameter (required)
  • after: Unique ID of the memory to start the query range at.
  • before: Unique ID of the memory to end the query range at.
  • limit: How many results to include in the response.
  • search: Search passages by text
  • ascending: Whether to sort passages oldest to newest (True, default) or newest to oldest (False)
  • user_id: user_id parameter

create_passage

  • ID: POST-v1-agents-agent-id-archival-memory
  • Description: Insert a memory into an agent's archival memory store.
  • Method: POST
  • Path: /v1/agents/{agent_id}/archival-memory

Parameters:

  • agent_id: agent_id parameter (required)
  • user_id: user_id parameter

modify_passage

  • ID: PATCH-v1-agents-agent-id-archival-memory-memory-id
  • Description: Modify a memory in the agent's archival memory store.
  • Method: PATCH
  • Path: /v1/agents/{agent_id}/archival-memory/{memory_id}

Parameters:

  • agent_id: agent_id parameter (required)
  • memory_id: memory_id parameter (required)
  • user_id: user_id parameter

delete_passage

  • ID: DELETE-v1-agents-agent-id-archival-memory-memory-id
  • Description: Delete a memory from an agent's archival memory store.
  • Method: DELETE
  • Path: /v1/agents/{agent_id}/archival-memory/{memory_id}

Parameters:

  • agent_id: agent_id parameter (required)
  • memory_id: memory_id parameter (required)
  • user_id: user_id parameter

list_messages

  • ID: GET-v1-agents-agent-id-messages
  • Description: Retrieve message history for an agent.
  • Method: GET
  • Path: /v1/agents/{agent_id}/messages

Parameters:

  • agent_id: agent_id parameter (required)
  • after: Message after which to retrieve the returned messages.
  • before: Message before which to retrieve the returned messages.
  • limit: Maximum number of messages to retrieve.
  • use_assistant_message: Whether to use assistant messages
  • assistant_message_tool_name: The name of the designated message tool.
  • assistant_message_tool_kwarg: The name of the message argument.
  • user_id: user_id parameter

send_message

  • ID: POST-v1-agents-agent-id-messages
  • Description: Process a user message and return the agent's response.
    This endpoint accepts a message from a user and processes it through the agent.
  • Method: POST
  • Path: /v1/agents/{agent_id}/messages

Parameters:

  • agent_id: agent_id parameter (required)
  • user_id: user_id parameter

modify_message

  • ID: PATCH-v1-agents-agent-id-messages-message-id
  • Description: Update the details of a message associated with an agent.
  • Method: PATCH
  • Path: /v1/agents/{agent_id}/messages/{message_id}

Parameters:

  • agent_id: agent_id parameter (required)
  • message_id: message_id parameter (required)
  • user_id: user_id parameter

create_agent_message_stream

  • ID: POST-v1-agents-agent-id-messages-stream
  • Description: Process a user message and return the agent's response.
    This endpoint accepts a message from a user and processes it through the agent.
    It will stream the steps of the response always, and stream the tokens if 'stream_tokens' is set to True.
  • Method: POST
  • Path: /v1/agents/{agent_id}/messages/stream

Parameters:

  • agent_id: agent_id parameter (required)
  • user_id: user_id parameter

create_agent_message_async

  • ID: POST-v1-agents-agent-id-messages-async
  • Description: Asynchronously process a user message and return a run object.
    The actual processing happens in the background, and the status can be checked using the run ID.
  • Method: POST
  • Path: /v1/agents/{agent_id}/messages/async

Parameters:

  • agent_id: agent_id parameter (required)
  • user_id: user_id parameter

reset_messages

  • ID: PATCH-v1-agents-agent-id-reset-messages
  • Description: Resets the messages for an agent
  • Method: PATCH
  • Path: /v1/agents/{agent_id}/reset-messages

Parameters:

  • agent_id: agent_id parameter (required)
  • add_default_initial_messages: If true, adds the default initial messages after resetting.
  • user_id: user_id parameter

create_group

  • ID: POST-v1-groups-
  • Description: Create a new multi-agent group with the specified configuration.
  • Method: POST
  • Path: /v1/groups/

Parameters:

  • user_id: user_id parameter
  • X-Project: X-Project parameter

list_groups

  • ID: GET-v1-groups-
  • Description: Fetch all multi-agent groups matching query.
  • Method: GET
  • Path: /v1/groups/

Parameters:

  • manager_type: Search groups by manager type
  • before: Cursor for pagination
  • after: Cursor for pagination
  • limit: Limit for pagination
  • project_id: Search groups by project id
  • user_id: user_id parameter

upsert_group

  • ID: PUT-v1-groups-
  • Description: Create a new multi-agent group with the specified configuration.
  • Method: PUT
  • Path: /v1/groups/

Parameters:

  • user_id: user_id parameter
  • X-Project: X-Project parameter

delete_group

  • ID: DELETE-v1-groups-group-id
  • Description: Delete a multi-agent group.
  • Method: DELETE
  • Path: /v1/groups/{group_id}

Parameters:

  • group_id: group_id parameter (required)
  • user_id: user_id parameter

send_group_message

  • ID: POST-v1-groups-group-id-messages
  • Description: Process a user message and return the group's response.
    This endpoint accepts a message from a user and processes it through through agents in the group based on the specified pattern
  • Method: POST
  • Path: /v1/groups/{group_id}/messages

Parameters:

  • agent_id: agent_id parameter (required)
  • user_id: user_id parameter

list_group_messages

  • ID: GET-v1-groups-group-id-messages
  • Description: Retrieve message history for an agent.
  • Method: GET
  • Path: /v1/groups/{group_id}/messages

Parameters:

  • group_id: group_id parameter (required)
  • after: Message after which to retrieve the returned messages.
  • before: Message before which to retrieve the returned messages.
  • limit: Maximum number of messages to retrieve.
  • use_assistant_message: Whether to use assistant messages
  • assistant_message_tool_name: The name of the designated message tool.
  • assistant_message_tool_kwarg: The name of the message argument.
  • user_id: user_id parameter

send_group_message_streaming

  • ID: POST-v1-groups-group-id-messages-stream
  • Description: Process a user message and return the group's responses.
    This endpoint accepts a message from a user and processes it through agents in the group based on the specified pattern.
    It will stream the steps of the response always, and stream the tokens if 'stream_tokens' is set to True.
  • Method: POST
  • Path: /v1/groups/{group_id}/messages/stream

Parameters:

  • group_id: group_id parameter (required)
  • user_id: user_id parameter

list_identities

  • ID: GET-v1-identities-
  • Description: Get a list of all identities in the database
  • Method: GET
  • Path: /v1/identities/

Parameters:

  • name: name parameter
  • project_id: project_id parameter
  • identifier_key: identifier_key parameter
  • identity_type: identity_type parameter
  • before: before parameter
  • after: after parameter
  • limit: limit parameter
  • user_id: user_id parameter

create_identity

  • ID: POST-v1-identities-
  • Description: Make a POST request to /v1/identities/
  • Method: POST
  • Path: /v1/identities/

Parameters:

  • user_id: user_id parameter
  • X-Project: X-Project parameter

upsert_identity

  • ID: PUT-v1-identities-
  • Description: Make a PUT request to /v1/identities/
  • Method: PUT
  • Path: /v1/identities/

Parameters:

  • user_id: user_id parameter
  • X-Project: X-Project parameter

retrieve_identity

  • ID: GET-v1-identities-identity-id
  • Description: Make a GET request to /v1/identities/{identity_id}
  • Method: GET
  • Path: /v1/identities/{identity_id}

Parameters:

  • identity_id: identity_id parameter (required)
  • user_id: user_id parameter

update_identity

  • ID: PATCH-v1-identities-identity-id
  • Description: Make a PATCH request to /v1/identities/{identity_id}
  • Method: PATCH
  • Path: /v1/identities/{identity_id}

Parameters:

  • identity_id: identity_id parameter (required)
  • user_id: user_id parameter

delete_identity

  • ID: DELETE-v1-identities-identity-id
  • Description: Delete an identity by its identifier key
  • Method: DELETE
  • Path: /v1/identities/{identity_id}

Parameters:

  • identity_id: identity_id parameter (required)
  • user_id: user_id parameter

list_models

  • ID: GET-v1-models-
  • Description: Make a GET request to /v1/models/
  • Method: GET
  • Path: /v1/models/

No parameters required.

list_embedding_models

  • ID: GET-v1-models-embedding
  • Description: Make a GET request to /v1/models/embedding
  • Method: GET
  • Path: /v1/models/embedding

No parameters required.

list_blocks

  • ID: GET-v1-blocks-
  • Description: Make a GET request to /v1/blocks/
  • Method: GET
  • Path: /v1/blocks/

Parameters:

  • label: Labels to include (e.g. human, persona)
  • templates_only: Whether to include only templates
  • name: Name of the block
  • identity_id: Search agents by identifier id
  • identifier_keys: Search agents by identifier keys
  • user_id: user_id parameter

create_block

  • ID: POST-v1-blocks-
  • Description: Make a POST request to /v1/blocks/
  • Method: POST
  • Path: /v1/blocks/

Parameters:

  • user_id: user_id parameter

modify_block

  • ID: PATCH-v1-blocks-block-id
  • Description: Make a PATCH request to /v1/blocks/{block_id}
  • Method: PATCH
  • Path: /v1/blocks/{block_id}

Parameters:

  • block_id: block_id parameter (required)
  • user_id: user_id parameter

delete_block

  • ID: DELETE-v1-blocks-block-id
  • Description: Make a DELETE request to /v1/blocks/{block_id}
  • Method: DELETE
  • Path: /v1/blocks/{block_id}

Parameters:

  • block_id: block_id parameter (required)
  • user_id: user_id parameter

retrieve_block

  • ID: GET-v1-blocks-block-id
  • Description: Make a GET request to /v1/blocks/{block_id}
  • Method: GET
  • Path: /v1/blocks/{block_id}

Parameters:

  • block_id: block_id parameter (required)
  • user_id: user_id parameter

list_agents_for_block

  • ID: GET-v1-blocks-block-id-agents
  • Description: Retrieves all agents associated with the specified block.
    Raises a 404 if the block does not exist.
  • Method: GET
  • Path: /v1/blocks/{block_id}/agents

Parameters:

  • block_id: block_id parameter (required)
  • user_id: user_id parameter

list_jobs

  • ID: GET-v1-jobs-
  • Description: List all jobs.
  • Method: GET
  • Path: /v1/jobs/

Parameters:

  • source_id: Only list jobs associated with the source.
  • user_id: user_id parameter

list_active_jobs

  • ID: GET-v1-jobs-active
  • Description: List all active jobs.
  • Method: GET
  • Path: /v1/jobs/active

Parameters:

  • user_id: user_id parameter

retrieve_job

  • ID: GET-v1-jobs-job-id
  • Description: Get the status of a job.
  • Method: GET
  • Path: /v1/jobs/{job_id}

Parameters:

  • job_id: job_id parameter (required)
  • user_id: user_id parameter

delete_job

  • ID: DELETE-v1-jobs-job-id
  • Description: Delete a job by its job_id.
  • Method: DELETE
  • Path: /v1/jobs/{job_id}

Parameters:

  • job_id: job_id parameter (required)
  • user_id: user_id parameter

health_check

  • ID: GET-v1-health-
  • Description: Make a GET request to /v1/health/
  • Method: GET
  • Path: /v1/health/

No parameters required.

create_sandbox_config_v1_sandbox_config__post

  • ID: POST-v1-sandbox-config-
  • Description: Make a POST request to /v1/sandbox-config/
  • Method: POST
  • Path: /v1/sandbox-config/

Parameters:

  • user-id: user-id parameter

list_sandbox_configs_v1_sandbox_config__get

  • ID: GET-v1-sandbox-config-
  • Description: Make a GET request to /v1/sandbox-config/
  • Method: GET
  • Path: /v1/sandbox-config/

Parameters:

  • limit: Number of results to return
  • after: Pagination cursor to fetch the next set of results
  • sandbox_type: Filter for this specific sandbox type
  • user-id: user-id parameter

create_default_e2b_sandbox_config_v1_sandbox_config_e2b_default_post

  • ID: POST-v1-sandbox-config-e2b-default

…(正文过长,页面只展示前面部分,完整内容见仓库)

常见问题

6 问
答案由本站依据条目字段整理,不引用上游原文
Elijahdev0 MCP 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Elijahdev0 MCP 怎么在 Claude 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Elijahdev0 MCP 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Elijahdev0 MCP 需要 API Key 吗?

资料标注为无需认证,装好就能连;如果实际调用时报鉴权错误,按官方文档补上凭据。

Elijahdev0 MCP 支持哪些客户端?

资料标注支持 Claude;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Elijahdev0 MCP 能提供哪些能力?

资料显示约 120 个工具;能力标签包括 API接口、JavaScript、Claude、工具管理。具体工具清单以官方文档为准。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。