Cie MCP Server

Cie MCP server exists for a simple reason — assistants are far more useful when they can act on Cie directly instead of describing what you should do. CIE - Code Intelligence Engine 20+ MCP tools that give AI agents semantic code search, call graph analysis, and endpoint discovery — 100% local, indexes 100k LOC in seconds..

What you get

• Semantic Search — - Find code by meaning, not just text matching
• Call Graph Analysis — - Trace execution paths including interface dispatch resolution
• MCP Native — - Works seamlessly with Claude Code, Cursor, and any MCP client
• Fast — - Indexes 100k LOC in seconds, queries in milliseconds
• Private — - All data stays local, your code never leaves your machine
• Accurate — - Keyword boosting ensures relevant results for function searches

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

What the assistant can call

Once Cie is connected, these are the calls the assistant has available:

• cie_list_endpoints — List HTTP/REST endpoints from common Go frameworks
• cie_list_services — List gRPC services and RPC methods from .proto files
• System — The System tool exposed by this server
• Testing — The Testing tool exposed by this server
• Building — The Building tool exposed by this server

Configuration and credentials

You will need 3 environment variables: OLLAMA_HOST, OPENAI_API_KEY, NOMIC_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the cie mcp server does with a few real requests.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Cie's toolset — cie_list_endpoints, cie_list_services, System and 2 more — is a fair guide to whether it matches your workflow. It is maintained by kraklabs; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.