Developer · Remote MCP server
Tentra - Memory for AI Coding Agents
Memory for AI coding agents. Call graphs + refactor safety + persistent code context. 35 MCP tools.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.rdanieli/tentra- Version
- 1.3.2
- Status
- Active
- Category
- developer
- Transport
- SSE (HTTP + Server-Sent Events), stdio (local process)
- Package
- npm
- Published
- 2026-04-20
- Updated
- 2026-04-20
- Publisher
- rdanieli (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/rdanieli) · how
- Repository
- github.com/rdanieli/tentra-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| SSE (HTTP + Server-Sent Events) | https://trytentra.com/api/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- SSE stream
- Not opened: sign-in required
- Sign-in required
- Yes - HTTP 401
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | tentra-mcp | 1.3.2 | stdio |
How to connect Tentra - Memory for AI Coding Agents
Tentra - Memory for AI Coding Agents is a remote MCP server reached over the older SSE transport, at https://trytentra.com/api/mcp. Clients that support remote servers generally still accept SSE endpoints, though the protocol now favours Streamable HTTP.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: tentra-mcp version 1.3.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y tentra-mcp@1.3.2. It reads the environment variable TENTRA_API_KEY (secret); set it in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"tentra": {
"command": "npx",
"args": [
"-y",
"tentra-mcp@1.3.2"
],
"env": {
"TENTRA_API_KEY": "<secret>"
}
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Tempreon - Personal AI MemoryPerson-owned AI memory that learns, not just stores - portable context for any MCP client. | Remote · HTTPLive check: sign-in required |
| TenantsdbMulti-tenant database orchestration: isolated Postgres, MySQL, MongoDB, Redis tenants on demand. | Remote · HTTPLive check: sign-in required |
| Tenki Sandbox MCPDisposable microVM sandboxes for AI agents: run code, read/write files, git, preview URLs. | Local · stdio |
| TensorcadDesign transformer LLM architectures and report their parameters, FLOPs, memory and cost. | Local · stdio |
| TeramindMCP server for Teramind's insider-threat/employee-monitoring API (read-only, metadata-only surface). | Local · stdio |
| TermadaPersistent, policy-controlled missions for AI agents operating local and SSH environments. | Local · stdio |
| TermcpAn MCP server that lets AI agents act like a human at a real terminal, local or over SSH. | Local · HTTP |
| Termdat MCPMCP server for TERMDAT - the terminology database of the Swiss Federal Administration. | Local · stdio |