MCP Adapter

The MCP adapter wraps the Studio API and exposes tool-style methods for agent runtimes like Claude Desktop, Cursor, and custom MCP hosts.

Use MCP when you want an AI agent to call controlled Studio tools instead of crafting raw HTTP requests.

1. Create a Studio API key in Settings → API & Agents with only the scopes your agent needs.
2. Build the MCP package.
3. Set environment variables in your agent host.
4. Register the MCP server command in your host config.
5. Run a first call like list_gear to verify connectivity and auth.

# inside geardex repo
pnpm --filter @geardex/mcp-geardex build

GEARDEX_BASE_URL=https://www.geardex.app
GEARDEX_STUDIO_API_KEY=gdx_live_your_key_here

You can use either https://www.geardex.app or https://geardex.app. The MCP adapter handles the domain alias redirect while preserving authentication.

Point your MCP host to the GearDex MCP server entrypoint and include env vars. This example works for Claude Desktop style MCP configs.

{
  "mcpServers": {
    "geardex": {
      "command": "node",
      "args": ["packages/mcp-geardex/dist/index.js"],
      "env": {
        "GEARDEX_BASE_URL": "https://www.geardex.app",
        "GEARDEX_STUDIO_API_KEY": "gdx_live_your_key_here"
      }
    }
  }
}

List my 5 most recent gear items and group them by type.
Then show the total count by type.

Request flow:

1. Your agent host invokes an MCP tool (for example list_shoots).
2. The GearDex MCP adapter maps that tool to a Studio API endpoint.
3. The adapter sends a bearer-token request using your scoped API key.
4. The Studio API enforces scopes, user ownership, and audit logging server-side.
5. The adapter returns structured JSON back to the host as MCP tool output.

Need raw endpoint schemas for custom clients? Use the OpenAPI document at /api/studio-agent/openapi.

High-value ways to use MCP with your Studio data:

Use GearDex MCP tools to generate a Monday brief:
1) list_shoots for the next 14 days
2) list_maintenance for scheduled/in_progress items
3) list_documents where warrantyStatus is warning or critical
4) get_analytics_summary

Return:
- risks
- upcoming workload
- inventory readiness summary

Use GearDex MCP tools to close this service ticket:
1) find_gear for "Sony A7S III"
2) create_maintenance with service_type "Sensor cleaning"
3) update_maintenance to completed when the ticket is closed

Only use write tools if the configured API key includes maintenance:write.

• Use one key per agent runtime.
• Grant minimum scopes required for that specific agent.
• Prefer expiring keys and rotate regularly.
• Revoke immediately if a host/workstation is compromised.
• Monitor audit activity in Settings → API & Agents.