MCP servers
Model Context Protocol (MCP) is an open standard for connecting an AI agent to external tools and data sources. Tempr's agent can use any MCP server you add, right alongside its built-in tools.
Browsing the catalog
Open the MCP panel inside the chat tool window to search and one-click install curated servers without leaving your IDE — the same catalog shown on the marketing site's MCP catalog. A few of the official servers you'll find there:
| Server | Publisher | What it does |
|---|---|---|
| Filesystem | Anthropic | Read and write files/directories on the local filesystem, scoped to a directory you choose. |
| Fetch | Anthropic | Fetch and convert web pages to Markdown for the model to read. |
| Memory | Anthropic | A persistent knowledge-graph memory the agent can read and write across a session. |
| GitHub | Official | Issues, pull requests, repos, and code search against GitHub. |
Adding a custom server
Not every server needs to come from the catalog. Add any MCP-compliant server manually with its command/args (for local stdio servers) or URL (for remote HTTP/SSE servers), and the agent will discover its tools automatically the next time it starts a turn.
Where MCP applies
MCP tool execution is part of the Chat agent loop — it runs alongside file edits and shell commands inside your IDE session. Tempr Gateway is a plain chat-completions API with no agent loop of its own, so MCP servers aren't invoked through Gateway; if you're building an agent against the Gateway API yourself, you own the tool-calling loop and can wire up MCP (or anything else) on your side using the tools parameter.