Resources

In addition to tools, the server exposes three read-only resource templates over the MCP protocol. Resources are URI-addressable read endpoints that clients can fetch directly without going through a tool call.

URI template	Returns
chordia://project/{project_id}/signals	Full signal catalog for the project
chordia://project/{project_id}/guidance	Full guidance catalog for the project
chordia://call/{session_id}/transcript	Raw transcript for a single call

Catalog resources

chordia://project/{project_id}/signals and …/guidance are convenience reads of the same data the get_signals and search_guidance tools return — narrowed to the project's locked verticals when applicable.

These resources are not behind tool-call auth — they're project-scoped reads of static catalog files. Project verticals (when locked) still filter the result.

Transcript resource

chordia://call/{session_id}/transcript is project-scoped via the connection's API key, not via the URI. The URI's session_id is checked against the auth-derived project_id, so a key for project A cannot retrieve a transcript belonging to project B even if it knows the session_id.

Returns:

{
  "session_id": "<id>",
  "metadata": {
    "session_id": "...",
    "agent_name": "...",
    "title": "...",
    "created_dt": "...",
    "interaction_direction": "inbound",
    "language": "en"
  },
  "transcript": [
    {"turn": 0, "actor": "customer", "text": "..."},
    {"turn": 1, "actor": "agent",    "text": "..."}
  ]
}

If the session doesn't exist (or is in another project / outside the caller's allowed_agents scope), the response is the standard 404-shaped error:

{ "error": "Call not found: <session_id>" }

Why resources, not tools?

The MCP protocol distinguishes the two:

• Tools are invoked — they take arguments and have side effects / can be expensive. The LLM decides when to call them.
• Resources are read — they're addressed by URI, typically cheap, and the client decides when to read them (often eagerly at session start).

So the three resources here are the read-only convenience surface; the 12 tools are the rich query surface.