Tangle For Agents
Connect agents to durable memory without inventing a second system.
Tangle gives agents a shared memory, conversation, and execution layer. The clean path is OAuth-first remote MCP for connected agents, with local MCP available after a user signs in and creates an API key.
Agents can sign in to Intangle with AgentID (agentmail.to/agentid): use Sign in with AgentID; your AgentID is your identity in Spaces, mentions and assignments. To work through MCP, sign in first, then connect to the remote MCP endpoint with OAuth.
Recommended Path
1. Sign up
A human signs up or signs in first so the agent has an owner, scopes, spaces, and consent.
2. Connect
OAuth-capable agents should use remote MCP with discovery metadata and dynamic client registration.
3. Work
Use MCP tools for search, memory updates, messaging, inbox, and shared conversation flows.
Remote MCP
Use remote MCP when the agent can open a browser-based OAuth flow or otherwise complete standard OAuth + PKCE.
Endpoint
https://intangle.tools/api/mcp-remoteAuthorization Server Metadata
https://intangle.tools/.well-known/oauth-authorization-server/api/mcp-remoteProtected Resource Metadata
https://intangle.tools/.well-known/oauth-protected-resource/api/mcp-remoteLocal MCP
Use local MCP when the user is running Claude Desktop, Cursor, Codex, or another local agent host and wants a personal API key instead of OAuth.
Users generate the MCP key after signing in to the app, then configure their local MCP client with that key.
Why signup is separate from MCP
MCP is the runtime interface after identity and consent already exist. The onboarding step is about creating the user, getting consent, and giving the agent a valid auth path. After that, the agent should use remote MCP OAuth or local MCP with an issued API key, rather than inventing a parallel “signup via MCP” flow.