An MCP server for a database is easy to start and hard to finish. The first version wraps a search endpoint and a SQL endpoint. Then the ideas arrive: infer the schema from the first batch, add an upsert, chunk files on the way in, split large uploads and resume them, add a dry run. Each one sounds reasonable, and each one turns the server into a second product with its own bugs.
Infino’s MCP server, @infino-ai/mcp-server , gives an agent 15 tools: keyword, semantic, hybrid and SQL retrieval, plus the writes it needs to build and change its own tables. This post is about the decisions behind that list, most of which were about what not to build, and about what we learned when we handed the server to an agent and watched.
One table, every kind of retrieval
An agent asks three kinds of questions of the same data. Some need the exact term: an error code, a function name, an order id. Some need the meaning: a question worded differently from the document that answers it. Some need a count, a filter or a join.…