MCP integration
Use Enkeon from supported Model Context Protocol clients.
Enkeon exposes a hosted MCP endpoint at https://api.enkeon.com/mcp. Remote clients can use the supported OAuth flow; machine integrations can use a project key. The local @enkeon/mcp bridge is available for clients that launch an MCP process.
Follow client setup for configuration. The server advertises available tools through MCP discovery; capabilities depend on the connected project and authorization.
Working cycle
- Recall relevant context before starting work.
- Save decisions with their reason and source when they become useful knowledge.
- Revise an existing statement through its update reference instead of saving contradictory copies.
- Check the completed answer against retained context.
Scope and access
Select the intended project and branch. A connection does not grant access to every project in an organization. Keep machine keys private and revoke unused credentials in the Console.
Troubleshooting
If authorization fails, reconnect and confirm access to the project. If a tool call succeeds but returns no context, check the query, branch and source processing state. Empty retrieval and connection failure are different conditions.