> For the complete documentation index, see [llms.txt](https://docs.living-memory.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.living-memory.app/connect-mcp.md). # Connect through MCP You need a client supporting remote Streamable HTTP MCP and access to the intended Space. Follow your client's current MCP connection UI or configuration instructions. ## Free capsule connection 1. Obtain the capsule's actual MCP credential URL privately. CLI users can find it with `lm inspect my-project`. 2. Add that URL as a remote Streamable HTTP MCP server in the client. 3. Let the client initialize and discover the offered tools. 4. Ask it to read memory state, then recall a harmless known fact. A token-bearing capsule URL is already a credential. The holder does not obtain safety from the absence of an additional login screen. Do not paste the URL into a public issue, shared screenshot or docs example. A write-capable connection should offer the appropriate memory writes. A read-only connection should offer reads and withhold writes. Discover tools on the actual connection rather than assuming a fixed tool count. ## Personal World connection Use `https://lme.viibe.to/mcp` as the account OAuth endpoint. Complete consent with the intended account. Authentication and World entitlement are separate; a signed-in account does not by itself prove access to a paid World. Expected result: the client reports available tools and a read returns data or state from the intended Space. A connected badge alone is insufficient. Opening an endpoint in a browser reads its entrance response; it does not send the MCP initialization and tool calls. Theatre visitor links are also distinct from MCP URLs. For client errors, see [Troubleshooting](/troubleshooting.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.living-memory.app/connect-mcp.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.