POMA AI MCP Server
POMA AI ships the poma-mcp Model Context Protocol (MCP) server for PrimeCut. It works with any MCP-aware client (Claude Code, Claude Desktop, Cursor, your own agent).
| Server | Tools it exposes | What it gives you |
|---|---|---|
poma-mcp | primecut_ingest, primecut_status, primecut_get_result, primecut_resume | PrimeCut document ingestion — returns parsed chunks + chunksets (and optionally the raw .poma archive). |
Authentication: poma-mcp reads POMA_API_KEY from the env, accepts -token as a CLI flag, accepts a per-call token arg, or (HTTP mode) reads x-api-key / Authorization: Bearer. Use an account-level key (poma_acc_…).
Need managed ingestion, retrieval and prompt-ready context behind one API instead of running your own vector stack? index4.ai, the managed RAG service built on PrimeCut, has its own hosted MCP server at
https://mcp.index4.ai— see the index4.ai MCP docs.
Common setup
Every MCP client uses the same shape — command + args + env for stdio servers. Pick the snippet that matches your client and continue on the poma-mcp page.
{
"mcpServers": {
"poma": {
"command": "/full/path/to/poma-mcp",
"args": ["-input", "-"],
"env": { "POMA_API_KEY": "your-api-key" }
}
}
}{
"mcpServers": {
"poma": {
"command": "/full/path/to/poma-mcp",
"args": ["-input", "-"],
"env": { "POMA_API_KEY": "your-api-key" }
}
}
}{
"mcpServers": {
"poma": {
"command": "/full/path/to/poma-mcp",
"args": ["-input", "-"],
"env": { "POMA_API_KEY": "your-api-key" }
}
}
}After saving, restart the client (Claude Desktop especially needs a full restart). Confirm the server is running by asking the agent to list its tools — you should see the primecut_* tools.
Authentication
poma-mcp accepts these credential sources:
| Source | Precedence | When to use |
|---|---|---|
POMA_API_KEY env var | lowest | Local development; one shared key per agent process. |
-token <key> CLI flag | middle | Long-running services where the env is fixed by platform. |
token in tool args | highest | Per-call override (e.g. multi-tenant proxy). |
x-api-key / Authorization: Bearer header | HTTP only | Static-key option for your own HTTP-mode deployment. |
Pages
poma-mcp— PrimeCut document-ingestion server (primecut_*tools).
See also
- index4.ai MCP server — hosted MCP for the managed RAG service built on PrimeCut.
- PrimeCut SDK — same ingestion flow, programmatic.
- POMA CLI — same workflow from the shell.