pragma.vision Your technology observatory

Agent connection guide

Connect your agent

Connect an MCP-capable client to the pragma.vision gateway, then use its plan-available tools to read derived readiness results and submit structured observations for validation.

These are third-party clients; the notes below document their public MCP connection formats.

MCP gateway · JSON-RPC 2.0 https://mcp.pragma.vision Streamable HTTP · POST requests use the root URL

Account access

Authentication

Clients connect to the root gateway and authenticate with OAuth 2.1 via my.soft.house. No separate license key is required.

Before sign-in, clients can discover the authorization flow at /.well-known/oauth-protected-resource. The resource metadata names https://my.soft.house as the authorization server.

A missing or rejected bearer receives 401 with error code invalid_token and a WWW-Authenticate resource_metadata challenge.

Copy-paste setup

Choose your client

Claude Code

claude mcp add --transport http pragma-vision https://mcp.pragma.vision

Then complete the OAuth sign-in when the client prompts.

Claude Desktop

Settings → Connectors → Add custom connector → name pragma.vision, URL https://mcp.pragma.vision, then sign in via my.soft.house when prompted.

Cursor

.cursor/mcp.json:

{
  "mcpServers": {
    "pragma-vision": { "url": "https://mcp.pragma.vision" }
  }
}

VS Code

.vscode/mcp.json:

{
  "servers": {
    "pragma-vision": { "type": "http", "url": "https://mcp.pragma.vision" }
  }
}

Any MCP client

JSON-RPC 2.0 over streamable HTTP at https://mcp.pragma.vision, Authorization: Bearer <token>; discovery at /.well-known/oauth-protected-resource; standard tools/list and tools/call methods.

Live entitlement

Plans and tool access

Free signed-in account

12 open tools

500 calls/day

Professional Watch

Adds evidence.drawer

5,000 calls/day

Founding Cohort

Adds evidence.drawer + signal.stream

20,000 calls/day

Browse the full tool inventory →

Current evidence

Data freshness

An automated collection lane refreshes register signals every six hours; verified changes flow into change events, watch notifications, and the published change digests.

Your opinion

Tell us anything.

What works, what doesn't, what's missing — especially about our watches, lenses, and the register itself. Anonymous is fine; leave an email if you'd like a reply.