OpenFactory MCP server

@openfactory/mcp lets MCP hosts submit signals to OpenFactory and inspect the issue inbox, factory floor, task details, and coding-agent sessions.

Configure

Create an OpenFactory API key with only the permissions the MCP host needs. A useful read/write set is:

• ingestion:events.create
• ingestion:requests.list
• openfactory:getIssues
• openfactory:getFloorTasks
• openfactory:getTaskDetail
• openfactory:getTaskAgentSession

Then add the server to your MCP host:

{
  "mcpServers": {
    "openfactory": {
      "command": "npx",
      "args": ["-y", "@openfactory/[email protected]"],
      "env": {
        "OPENFACTORY_BASE_URL": "https://factory.example.com",
        "OPENFACTORY_API_KEY": "ofk_...",
        "OPENFACTORY_TEAM_ID": "team_..."
      }
    }
  }
}

OPENFACTORY_TEAM_ID is optional when the host only uses request ingestion or request history tools. The CLI requires one of OPENFACTORY_API_KEY, OPENFACTORY_ACCESS_TOKEN, or OPENFACTORY_INGEST_TOKEN.

Manual task creation, starting work on an issue, and messaging a coding agent currently require OPENFACTORY_ACCESS_TOKEN, because those OpenFactory API operations require a human session. API keys can use the read tools and request ingestion according to their configured permission grants.

Tools

• openfactory_create_request
• openfactory_list_requests
• openfactory_list_issues
• openfactory_list_tasks
• openfactory_get_task
• openfactory_get_agent_session
• openfactory_create_task
• openfactory_start_issue
• openfactory_send_agent_message

Development

npm install
npm test
npm run typecheck
npm run build

Release

npm run release:dry     # test, build, and inspect the package without publishing
npm run release         # publish the next patch version
npm run release minor   # or major / an explicit version such as 0.2.0

The release command requires npm authentication, publishes the package, commits the version bump, creates an mcp-v<version> tag, and pushes the commit and tags.