Connect AIeph
AIeph is an MCP server. Add it to your AI coding agent, and the agent checks the shared cache before your model generates an answer.
On a cache hit, your agent gets a known answer instantly. On a miss, AIeph stays silent and your model answers exactly as it normally would — it never guesses.
mcpServers; VS Code uses servers. Copy the block for your tool exactly.Cursor
1. Create the config file.
- For one project:
.cursor/mcp.jsonin the project root. - For all projects:
~/.cursor/mcp.json(your home folder).
2. Paste this in:
{
"mcpServers": {
"aieph": {
"url": "https://aieph.dev/mcp"
}
}
}
3. Reload. Cursor picks up the server automatically. Open the MCP settings (Settings → MCP) and confirm aieph shows a green/connected status and that aieph_search appears in its tool list.
Claude Code
Option A — one command (recommended)
claude mcp add --transport http aieph https://aieph.dev/mcp
By default this registers AIeph for the current project only. To make it available in every project instead:
claude mcp add --transport http --scope user aieph https://aieph.dev/mcp
To share it with your team via a committed .mcp.json file:
claude mcp add --transport http --scope project aieph https://aieph.dev/mcp
Option B — edit .mcp.json by hand
Project root:
{
"mcpServers": {
"aieph": {
"type": "http",
"url": "https://aieph.dev/mcp"
}
}
}
Verify: run claude mcp list. aieph should show as connected. No sign-in step is needed (AIeph requires no authentication).
VS Code
Requires the GitHub Copilot extension. MCP tools only run in Agent mode.
1. Create the config file.
- For one workspace:
.vscode/mcp.jsonin the project root. - For all workspaces: open the Command Palette (
Cmd/Ctrl+Shift+P) → run MCP: Open User Configuration.
2. Paste this in (note the top-level key is servers, not mcpServers):
{
"servers": {
"aieph": {
"type": "http",
"url": "https://aieph.dev/mcp"
}
}
}
3. Reload the window. Command Palette → Developer: Reload Window.
4. Switch Copilot Chat to Agent mode. Open the Copilot Chat panel and change the mode dropdown from Ask to Agent — MCP tools do nothing in Ask mode. The aieph_search tool should now appear in the tools list.
JetBrains IDEs
IntelliJ IDEA, WebStorm, PyCharm, GoLand, RubyMine, and more. Requires the bundled AI Assistant plugin and a JetBrains AI subscription (a free trial works). Steps below are for AI Assistant 2026.x.
1. Open the MCP settings. Go to Settings (Ctrl + Alt + S) → Tools → AI Assistant → Model Context Protocol (MCP). (Or, in the AI chat, type / and choose Add Command.)
2. Add a server. Click the Add (+) button. The New MCP Server dialog opens.
3. Choose the HTTP connection type and paste this JSON:
{
"mcpServers": {
"aieph": {
"url": "https://aieph.dev/mcp"
}
}
}
4. Set the server level — choose Global (all projects) or Project (this project only).
5. Click OK, then Apply. Applying starts the connection. Watch the Status column turn to connected. Click the icon in the Status column to see the available tools; aieph_search should be listed.
npx with args ["mcp-remote", "https://aieph.dev/mcp"]. Upgrading AI Assistant is the cleaner fix.Verify it's working
In any of the four tools, ask your agent an error, library, or version question, for example:
Your agent should call aieph_search before answering. If the cache has a match, you get it instantly. If not, the tool returns nothing and your model answers as usual — that's expected. A miss is silent by design; a wrong cached answer would be worse than none.
Troubleshooting
- Tool never appears: restart/reload the client after editing config. Most MCP config changes require a full restart.
- Tool appears but never fires (VS Code): you're in Ask mode. Switch Copilot Chat to Agent mode.
- Wrong config key: VS Code uses
servers; Cursor and JetBrains usemcpServers. A block copied from the wrong tool will silently fail to load. - Connection fails: confirm the endpoint is reachable —
https://aieph.dev/mcp. No token or header is required.