docs: add Meko Remote MCP Server connection guide - #1171
Draft
thierrypdamiba wants to merge 3 commits into
Draft
Conversation
Meko hosts a remote MCP server for agent memory at mcp.mekodata.ai, built on YugabyteDB. This adds the connection guide alongside the other remote MCP server vendors, following the same structure. Covers the datapack model and the grant levels that decide what a gateway can reach, OAuth 2.0 setup via Meko's dynamic client registration, the static-key alternative and why it collapses per-user identity, and a troubleshooting section for the behaviors that surprise people once a second person joins a workspace. Verified against a live gateway with two accounts: 23 tools discovered, 8 exposed through a gateway, called from Claude Code. Promotion, grant enforcement, and cross-member isolation confirmed end to end. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
- Memory is private to the user, attributed to the agent. memory_search spans all of that user's agents. - Every grant sees all 23 tools. Meko denies memory_promote at call time rather than hiding it, so the tool list does not vary by grant. - Any grant can connect and use the memory, conversation, and knowledge base tools. Owner or maintainer is needed only for memory_promote. - Static key: agent_id attribution survives because it is a tool argument. What is lost is per-user identity and grants. Keys are account-scoped and expire after 365 days. - Note the default datapack name, the Connect dialog as a second place to create keys, and the v2.1.0 removal of tool-level scope arguments. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a connection guide for Meko, which hosts a remote MCP server for agent memory at
mcp.mekodata.ai, built on YugabyteDB. Placed alongside the other remote MCP server vendors and following the same structure as the recent Salesforce, HubSpot, Snowflake, and GitHub guides.Requested by Yugabyte in #ext-arcade-x-yugabyte. They will publish a mirror on their docs site linking back.
What it covers
owner,maintainer,contributor,viewer) that decide what a gateway can reachVerification
Tested against a live gateway with two real Meko accounts, an owner and a contributor:
memory_promotereturnsonly datapack owners and maintainers are allowedfor a contributor, enforced at call time with the tool still listedmemory_searchstops returning the item,knowledgebase_searchstarts, and provenance (agent_id, originatingmemory_id) survivesOpen item
The end-to-end verification above ran on the static-key path. The OAuth authorization leg is written from Meko's advertised OAuth 2.1 support and a successfully registered client, but I have not completed the consent flow start to finish. Reviewers should treat the OAuth steps as unconfirmed until I do, and I will follow up in this PR either way.
🤖 Generated with Claude Code