Idf Mcp
Expose an Intent-Driven Framework (IDF) domain—booking, planning, invest, etc.—as typed MCP tools so Claude Code or Cursor can call your business rules safely.
Overview
io.github.intent-driven-software/idf-mcp is a Build-phase MCP server that exposes an IDF domain from a host runtime as MCP tools with invariants and role scopes in each tool description.
What is this MCP server?
- Bootstraps or attaches to an existing IDF host via IDF_SERVER and IDF_DOMAIN
- Embeds domain invariants and role scopes directly in MCP tool descriptions for safer agent calls
- Optional ontology bootstrap from IDF_ONTOLOGY_PATH when IDF_BOOTSTRAP=1
- Ships as npm @intent-driven/mcp-server v1.0.2 over stdio transport
- Supports secret IDF_AUTH_TOKEN when the host requires authenticated access
- Package version 1.0.2
- npm identifier @intent-driven/mcp-server
What problem does it solve?
Agents calling your domain logic through ad-hoc APIs ignore business rules and blow past role boundaries.
Who is it for?
Solo builders already using Intent-Driven Framework who want agent-safe, ontology-backed tool surfaces without rewriting every action by hand.
Skip if: Teams without an IDF host, ontology, or appetite to run and secure a domain runtime locally or in their own infra.
What do I get? / Deliverables
After you configure the host URL, domain name, and optional ontology bootstrap, your agent gets scoped MCP tools that describe what is allowed before it acts.
- Stdio MCP tool catalog backed by your IDF domain
- Tool descriptions that surface invariants and role scopes to the agent
- Optional first-connection bootstrap from your ontology module
Recommended MCP Servers
Journey fit
Canonical shelf is Build because you wire a running IDF host and ontology into the agent stack after product shape is chosen, not during raw ideation. agent-tooling fits turning a domain runtime into MCP tools with invariants and role scopes embedded in every tool description.
How it compares
Domain-runtime MCP bridge with invariant-aware tool copy, not a generic REST wrapper or a planning skill.
Common Questions / FAQ
Who is idf-mcp for?
Indie and small teams on Intent-Driven Software who need coding agents to interact with a specific IDF domain under the same invariants the runtime enforces.
When should I use idf-mcp?
Use it during Build when your IDF host is running and you want stdio MCP tools for a named domain instead of custom agent prompts per endpoint.
How do I add idf-mcp to my agent?
Install @intent-driven/mcp-server from npm, set IDF_SERVER and IDF_DOMAIN (plus IDF_ONTOLOGY_PATH if IDF_BOOTSTRAP=1), add the server to Claude Code or Cursor MCP config, and restart the client.