innernet-mcp

Read-only MCP server over your Innernet graph. Ask your agent about your own network.

{
  "mcpServers": {
    "innernet": {
      "command": "npx",
      "args": ["-y", "innernet-mcp"],
      "env": { "INNERNET_DB_URL": "postgres://user:pass@localhost:5432/innernet" }
    }
  }
}

Or let the CLI write it for you:

pnpm innernet mcp --install

Tools

| Tool | What it answers | |---|---| | search_people | Find someone by name, email, company, title, or handle | | get_person | The full dossier for one person — every fact with the source it came from | | recent_contact | Who you have actually been in touch with lately | | gone_quiet | Real history, no recent contact. The reconnect list |

Read-only, by construction

Every tool is a SELECT. The server has no write path at all — an agent that can rewrite your relationship history is a much worse trade than one that can only read it.

Point INNERNET_DB_URL at a read-only Postgres role in any setting you care about. The server never needs write access, so granting it is pure downside.

Notes

• Requires a database built by innernet-cli.
• Facts carry a source_url and a confidence value. Treat low confidence as a lead, not a fact — a name match is not a person.
• A missing INNERNET_DB_URL is returned to the agent as an error message rather than thrown, so the model can explain what is wrong instead of the call dying.

MIT