# Meko MCP MCP Server > **Meko MCP MCP Server** is a hosted, multitenant Model Context Protocol (MCP) server run by **MewCP** (https://mewcp.com), giving AI agents managed access to Meko MCP. > > MewCP takes care of all MCP infrastructure for you — credential storage, OAuth flows, > token refresh, and production-grade auto-scaling — so your AI agents can connect to > third-party services and run freely without you managing any MCP server yourself. > > Server page: https://mewcp.com/mcp/meko-mcp > MewCP docs: https://docs.mewcp.com > Full catalog: https://mewcp.com/llms.txt --- ## About Meko provides a shared, persistent memory and knowledge layer for AI agents and teams. Store and retrieve conversation history, extract searchable facts, manage long-term memories, upload and search knowledge-base documents, share context across agents and teammates, and track agent execution traces across sessions and AI platforms. --- ## Details - Server ID: `meko-mcp` - Version: 3.2.4 - Tools: 42 - Authentication: OAuth, managed by MewCP - Transport: http --- ## Access The gateway URL below serves your **entire MewCP toolset**, not this server on its own. Pasting a config snippet is not enough — Meko MCP has to be in the toolset first. In order: 1. Add Meko MCP to your toolset at https://mewcp.com/mcp/meko-mcp 2. Connect your Meko MCP account (OAuth); MewCP stores the credential and attaches it to each call 3. Copy your MewCP API key from the dashboard (Developer) 4. Configure your client with the snippet for it below Once connected, an agent does **not** see this server's tools as top-level tools. It sees four meta-tools and reaches everything through them: - `search(query)` — find tools by keyword across the toolset - `get_schema(tools)` — full description and arguments for the tools you picked - `list_accounts(provider)` — only when one app has several connected accounts - `call_tool(server_maskedId, tool_name, args)` — execute So the list below is what `search` can return for this server, not a set of callable tool names on their own. --- ## Tools (42) Descriptions are truncated to 160 characters; call `get_schema` for the full text and the argument schema. Where a tool is annotated, its type is shown — treat `destructive` as irreversible. - `knowledgebase_search` _(read)_ — Hybrid search across the knowledgebase. Invoke when the user asks to **search**, **find**, or **look up** information in their knowledgebase or uploaded… - `knowledgebase_delete_document` _(destructive)_ — Permanently delete ONE knowledge-base file (document) from a datapack. This cannot be undone: the document's chunks and metadata are removed in one… - `context_search` _(read)_ — One retrieval call across the conversation cache, memory, and the knowledgebase — queries every source ``force_source`` allows **in parallel** and returns each… - `memory_add` _(write)_ — Store a fact as a long-term memory. Invoke when the caller has an explicit fact to persist: the user has asked to save something, the fact appears only in the… - `memory_delete_by_id` _(destructive)_ — Permanently delete a single memory by its UUID. This cannot be undone. - `memory_search` _(read)_ — Hybrid search across stored memories. Combines semantic (vector) similarity with keyword matching and an entity boost: memories that mention the specific… - `memory_get_by_id` _(read)_ — Retrieve a single memory by its UUID. - `memory_get_all` _(read)_ — List memories for the current datapack, one page at a time. Each call returns one page plus ``total`` and ``total_pages``. To read every memory, call again… - `memory_promote` _(destructive)_ — Promote memories into the datapack's shared knowledge base. Moves each memory out of the agent's private mem0 store into the tenant knowledge base + promoted… - `memory_update` _(write)_ — Overwrite an existing memory's text by its UUID. - `memory_delete_all` _(destructive)_ — Permanently delete memories. This cannot be undone. Deletes every memory that matches ALL of: this ``agent_id``, the calling user, this ``datapack_id``, and,… - `conversation_create` _(write)_ — Create a new conversation to store a chat / dialog exchange. Invoke when the user asks to **store**, **save**, or **log a conversation**, **chat history**, or… - `conversation_add_message` _(write)_ — Add a message (user prompt + assistant response) to a conversation. Call after ``conversation_create`` to append each message. A message represents one… - `conversation_get` _(read)_ — Retrieve a stored conversation by ID, optionally including its turns. Use this when the user asks to **recall**, **retrieve**, or **review** a previously… - `conversation_list` _(read)_ — List stored conversations for a datapack, ordered by most recently updated. Use this when the user asks to **list**, **show**, or **browse** the stored… - `conversation_update` _(write)_ — Update a conversation's title and/or metadata. - `conversation_delete` _(destructive)_ — Permanently delete a conversation and all its messages. This is a hard delete — the conversation and all associated traces are removed from Langfuse. This… - `datapack_create` _(write)_ — Create a new Meko datapack — an isolated database environment with its own agent namespace. Use this when the user asks to **create**, **provision**, or **set… - `datapack_list` _(read)_ — List the Meko datapacks visible to the current user. Use this when the user asks to **list**, **show**, or **view all** datapacks, workspaces, or environments.… - `datapack_search` _(read)_ — Search the Meko datapacks visible to the current user, one page at a time. Use this to **find a datapack's id**, to show the user some datapacks to choose… - `datapack_describe` _(read)_ — Describe a Meko datapack by id, optionally including status info. Use this when the user asks to **describe**, **get details**, or **inspect** a specific… - `datapack_update` _(write)_ — Update a Meko datapack's name, description, and/or conversation-search opt-out. Use this when the user asks to **rename**, **update**, or **change the… - `datapack_delete` _(destructive)_ — Permanently delete a Meko datapack, dropping its database and all roles. Use this when the user asks to **delete**, **destroy**, or **remove** a datapack. This… - `track_token_usage` _(write)_ — Record a token-usage GENERATION observation under the conversation trace. Lets external callers (the inference gateway, future services) attribute LLM /… - `artifact_put` _(write)_ — Upload a file artifact to this datapack. Use this when an agent has generated a file (report, CSV, PDF, code output, etc.) and wants to persist it in Meko for… - `artifact_get` _(read)_ — Retrieve a previously uploaded artifact by its content hash. Use this when the agent needs to read back a file it (or another agent) previously stored via… - `knowledgebase_upload_document` _(write)_ — Request a presigned S3 URL for uploading a file to this datapack's Knowledge Base. Use this when the file's content should be searchable later: docs, manuals,… - `knowledgebase_document_status` _(read)_ — Check the upload and indexing status of a file previously uploaded via knowledgebase_upload_document. Poll this with the `key` from… - `amp_cluster_create` _(write)_ — Create a cluster (a Postgres database) in a datapack. Use when the user asks to **create**, **provision**, or **spin up** a database/cluster. The datapack's… - `amp_cluster_list` _(read)_ — List the clusters (databases) in a datapack. Use when the user asks to **list**, **show**, or **view** databases/clusters. - `amp_cluster_get` _(read)_ — Get a single cluster (database) by id. - `amp_cluster_delete` _(destructive)_ — Delete a cluster (database), cascading to its branches and compute. Use when the user asks to **delete**, **drop**, or **remove** a database/cluster.… - `amp_branch_create` _(write)_ — Fork a branch in a cluster — a zero-copy, copy-on-write clone of the data. Use when the user asks to **branch**, **fork**, or **clone** a database so… - `amp_branch_list` _(read)_ — List the branches in a cluster (the default branch plus its forks). - `amp_branch_get` _(read)_ — Get a single branch by id. - `amp_branch_delete` _(destructive)_ — Delete a branch, cascading to its compute. Use when the user asks to **delete**, **drop**, or **remove** a branch. A branch that still has child branches is… - `amp_compute_create` _(write)_ — Provision a compute instance (an endpoint) on a branch. Use when the user asks to **create**, **provision**, or **attach** compute / an endpoint so a branch is… - `amp_compute_list` _(read)_ — List the compute instances (endpoints) on a branch. - `amp_compute_get` _(read)_ — Get a single compute instance (endpoint) by id — including its address. - `amp_compute_delete` _(destructive)_ — Retire a compute instance (endpoint) on a branch. Use when the user asks to **delete**, **stop**, or **remove** compute / an endpoint. Blocks until the… - `amp_compute_resize` _(write)_ — Resize a compute instance (endpoint) — change its CPU and/or memory. Use when the user asks to **resize**, **scale**, or change the **CPU/memory** of an… - `amp_core_budget` _(read)_ — Get the account's AMP vCPU budget: cores used across ALL datapacks vs the tier cap. Use BEFORE proposing a sized operation (``amp_cluster_create`` with… --- ## Connect Gateway URL: https://gateway.mewcp.com/personal/mcp Every request carries one header: Authorization: Bearer Replace `API_KEY` with your own key from the dashboard (Developer). ## Apps ### Claude Desktop Mac & Windows app - macOS: `~/Library/Application Support/Claude/claude_desktop_config.json` - Windows: `%APPDATA%\Claude\claude_desktop_config.json` ```json { "mcpServers": { "mewcp": { "command": "npx", "args": [ "-y", "mcp-remote@latest", "https://gateway.mewcp.com/personal/mcp", "--header", "Authorization:${AUTH_HEADER}" ], "env": { "AUTH_HEADER": "Bearer API_KEY" } } } } ``` Already have an "mcpServers" section in your config? Just add the server entry inside it. 1. Open Claude Desktop → Settings → Developer → "Edit Config" 2. Paste the snippet inside the outer { } of the config file (merge with your existing "mcpServers" section if you have one) 3. Save the file, then quit Claude Desktop completely and reopen it 4. Start a new conversation — your tool will be available ### VS Code Copilot / Cline - Command Palette → "MCP: Open User Configuration" (opens mcp.json). For one project only, use .vscode/mcp.json instead. ```json { "mcp.servers": { "mewcp": { "type": "http", "url": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have a "servers" section in your mcp.json? Just add the server entry inside it. 1. Open VS Code → Command Palette (Cmd+Shift+P / Ctrl+Shift+P) 2. Run "MCP: Open User Configuration" to open your mcp.json 3. Paste the snippet and save 4. Start the server when prompted (or from the MCP servers view) and use it in Copilot Chat ### Cursor AI-first editor - macOS: `~/.cursor/mcp.json` - Windows: `%USERPROFILE%\.cursor\mcp.json` ```json { "mcpServers": { "mewcp": { "url": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have an "mcpServers" section in your mcp.json? Just add the server entry inside it. 1. Open Cursor → Settings → Cursor Settings → MCP 2. Click "Add new global MCP server" 3. Paste the snippet and save 4. Restart Cursor ### Codex OpenAI's CLI agent - Add the snippet to your Codex MCP config or your standard MCP config file for the CLI tool you use. ```json { "mcpServers": { "mewcp": { "type": "http", "url": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Codex generally reads a standard MCP server block, so you can add this alongside your other configured servers. 1. Open your Codex MCP config or project-level config file 2. Paste the MewCP server block inside the config JSON/TOML structure your tool expects 3. Save the file and restart Codex 4. Verify the tool is available inside a fresh session ### Claude Code Anthropic's CLI agent - ~/.claude.json (user scope) or .mcp.json in your project root — create it if it doesn't exist. Or skip the file and use the CLI command below. ```json { "mcpServers": { "mewcp": { "type": "http", "url": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have an "mcpServers" section in your config? Just add the server entry inside it. 1. Open ~/.claude.json (or .mcp.json in your project root) in a text editor 2. Paste the snippet inside the outer { } (merge with your existing "mcpServers" section if you have one) 3. Save the file and start (or restart) Claude Code 4. Or skip the file entirely and run the CLI command below instead ### OpenCode Open-source terminal agent - ~/.config/opencode/opencode.json (global) or opencode.json in your project root — create it if it doesn't exist. ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "mewcp": { "type": "remote", "url": "https://gateway.mewcp.com/personal/mcp", "enabled": true, "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have an "mcp" section in your opencode.json? Just add the server entry inside it. 1. Open ~/.config/opencode/opencode.json (or opencode.json in your project root) in a text editor 2. Paste the snippet inside the outer { } (merge with your existing "mcp" section if you have one) 3. Save the file and start (or restart) OpenCode ### OpenClaw Self-hosted agent gateway - ~/.openclaw/openclaw.json — create it if it doesn't exist. ```json { "mcp": { "servers": { "mewcp": { "transport": "streamable-http", "url": "https://gateway.mewcp.com/personal/mcp", "enabled": true, "headers": { "Authorization": "Bearer API_KEY" } } } } } ``` Already have an "mcp" section in your openclaw.json? Just add the server entry inside "servers". 1. Open ~/.openclaw/openclaw.json in a text editor 2. Paste the snippet inside the outer { } (merge with your existing "mcp" section if you have one) 3. Save the file and restart OpenClaw ### Antigravity Google's agentic IDE - ~/.gemini/config/mcp_config.json (global) or .agents/mcp_config.json (workspace-local) — create it if it doesn't exist. ```json { "mcpServers": { "mewcp": { "serverUrl": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have an "mcpServers" section in your config? Just add the server entry inside it. Remote servers must use the "serverUrl" field — the legacy "url"/"httpUrl" fields aren't supported. 1. In the editor's agent side panel, click "…" → "MCP Servers" → "Manage MCP Servers" → "View raw config" (Antigravity CLI: type /mcp instead to open the Interactive MCP Manager) 2. Paste the snippet inside the outer { } (merge with your existing "mcpServers" section if you have one) 3. Save the file — the server connects automatically ### Hermes Nous Research's CLI agent - config.yaml in your Hermes config directory (~/.hermes) — add this under a top-level "mcp_servers:" key. ```yaml mcp_servers: mewcp: url: "https://gateway.mewcp.com/personal/mcp" headers: Authorization: "Bearer API_KEY" ``` Already have an "mcp_servers" section in your config.yaml? Just add the server entry inside it. 1. Open config.yaml in your Hermes config directory 2. Paste the snippet under the top-level "mcp_servers:" key (merge with existing entries if you have any) 3. Save the file, then run /reload-mcp in Hermes (or start a fresh session) 4. Ask Hermes "Tell me which MCP-backed tools are available right now" to confirm it connected ### DeepSeek Harness DeepSeek's agent harness - cordis.yml in your DSH project — or the patch file you mount plugins from. ```yaml - id: mcp-mewcp name: '@deepseek-ai/dsh-mcp-client' config: serverName: mewcp transport: streamable-http url: https://gateway.mewcp.com/personal/mcp headers: Authorization: "Bearer API_KEY" ``` One plugin instance = one MCP server. Add this entry to your plugin list; don't nest it inside another entry. 1. Open cordis.yml (or your patch file) in your DSH project 2. Paste the entry into your plugin list, keeping the leading dash and indentation 3. Restart DSH (or let HMR reload) — tools register as mcp__mewcp__ 4. Verify with: dsh web --dump-config | grep -A3 mcp ## SDKs ### Python fastmcp client ```python import asyncio from fastmcp import Client from fastmcp.client.transports import StreamableHttpTransport SERVER_URL = "https://gateway.mewcp.com/personal/mcp" API_KEY = "API_KEY" transport = StreamableHttpTransport( url=SERVER_URL, headers={ "Authorization": f"Bearer {API_KEY}", } ) async def main(): client = Client(transport) async with client: tools = await client.list_tools() print(tools) asyncio.run(main()) ``` 1. Install fastmcp: pip install fastmcp 2. Copy the snippet into your project 3. Replace API_KEY with your key from the dashboard 4. Run your script ### TypeScript MCP SDK ```typescript import { Client } from "@modelcontextprotocol/sdk/client/index.js"; import { StreamableHTTPClientTransport } from "@modelcontextprotocol/sdk/client/streamableHttp.js"; const SERVER_URL = "https://gateway.mewcp.com/personal/mcp"; const API_KEY = "API_KEY"; const transport = new StreamableHTTPClientTransport(new URL(SERVER_URL), { requestInit: { headers: { Authorization: `Bearer ${API_KEY}`, }, }, }); const client = new Client({ name: "mewcp-client", version: "1.0.0" }); await client.connect(transport); const tools = await client.listTools(); console.log(tools.tools.map((t) => t.name)); ``` 1. Install: npm install @modelcontextprotocol/sdk 2. Copy the snippet into your project 3. Replace API_KEY with your key from the dashboard 4. Run with Node 18+ as an ES module (e.g. npx tsx script.ts)