MCP Server
Connect any MCP-compatible AI agent to Hebbrix memory, temporal graph, reasoning, and Outcome Memory tools through one hosted endpoint.
Quick setup
Add the hosted Hebbrix endpoint to your client's MCP server configuration, save, and reconnect. Guest access does not require an account, API key, local process, or package installation.
{
"mcpServers": {
"hebbrix": {
"url": "https://mcp.hebbrix.com/mcp"
}
}
}https://mcp.hebbrix.com/mcp as the URL.Connection details
| Setting | Value |
|---|---|
| Server URL | https://mcp.hebbrix.com/mcp |
| Transport | Hosted HTTPS MCP |
| Guest authentication | Not required |
| Hosted server version | v0.5.7 |
| Tool surface | 26 tools |
What the MCP server exposes
The 26-tool surface covers memory, temporal graph, grounded reasoning, account workflows, and learning from explicitly reported outcomes. Representative tools include:
hebbrix_rememberstores durable memory from an agent interaction.hebbrix_askanswers using memory and temporal graph evidence.hebbrix_graph_queryqueries entities, relationships, timelines, and current truth.hebbrix_choose_actionrecords a decision receipt and chooses from measured outcome evidence.
Grounding and safety contract
Retrieval tools return only evidence that the API marked as grounded. Each verified response includes the grounding state, evidence memory IDs, and a claim receipt. If the upstream response is malformed, missing its safety envelope, degraded, or ungrounded, the hosted adapter fails closed instead of presenting related text as an answer.
Verify the connection
- Reconnect your client and confirm that the Hebbrix tools appear.
- Ask the agent to remember a distinctive, non-sensitive fact.
- Start a fresh conversation and ask the agent to retrieve that fact.
- For graph validation, store two related facts and query their relationship or timeline.
Guest and account-scoped use
Guest access is the quickest way to evaluate the hosted MCP connection. Applications that need account-owned collections, explicit tenant scoping, API administration, billing, or production data controls should use an authenticated Hebbrix account and follow the authentication guide.
Coding-agent workflows
For code-change history, previous-error lookup, fix tracking, and the dedicated/v1/coding-agent/* API surface, continue to the coding-agent guide.