MCP transport & tool discovery
One tool registry across remote HTTP, stdio and REST.
On this page
Remote MCP
The server is https://weeveo.com/api/v1/mcp and uses Streamable HTTP. OAuth discovery and authentication challenges let compatible hosts begin sign-in. API-key clients send Authorization: Bearer <key> as a request header. Do not put the key into the endpoint URL.
Discover tools
MCP tools/list exposes the same registered capabilities as the REST tool catalog. Each tool has a name, title, description, input schema and read/write metadata. Scope and workspace roles are enforced when a tool is called; listing a tool is not permission to execute every operation.
Local stdio server
For operators running the source checkout, the web package supplies mcp:stdio. Set WEEVEO_API_KEY to a valid saved key and configure a trusted local client's command to run that script with the required server database/storage environment. The process verifies the key and its current access. Stdio is a local server process, not a replacement public URL, and must not expose its environment secrets to untrusted users.
pnpm --filter @weeveo/web mcp:stdioMulti-site tools
First call list_projects. A multi-site OAuth credential has no automatic default project; pass the intended projectId to each site-specific tool. A newly created site needs a new connection before the old credential can read it.
Write operations
The registry marks writes, destructive operations and external actions. Read-only credentials cannot invoke writes. Most management changes also need an administrator role; funnel and goal operations have their own member requirement. See each tool's description and permissions.
Identity advertised to clients
MCP initialization supplies Weeveo's name, description, website and icon. The protocol does not define a universal publisher-name field. A host's plugin listing/publisher identity is configured separately; see app metadata.
Still looking for an answer? Try troubleshooting or get in touch.