Where do I create an MCP connection?

Personal space → MCP. Create a connection, copy the omk_ secret once, then follow the client-specific steps on that page or in the API documentation (MCP section).

Can I use my admin API key for MCP?

No. Admin osk_ keys work only on /api/v1. MCP requires a personal omk_ key from Personal space → MCP.

Which AI client is recommended?

Claude Code — native HTTP transport with Bearer auth, no mcp-remote proxy required.

Who owns records created via MCP?

You do. created_by and updated_by reflect the member who owns the MCP connection.

Connect Claude to your CRM — from Personal space

Issue a personal omk_ key from Personal space → MCP. Remote MCP at /api/mcp lets Claude Code, Claude Desktop, and Cursor search and update records within your permission profile.

MCP tools

Records, schema, import, attachments

omk_

Member keys

Personal space → MCP only

RLS

Same profile

Matches Operations permissions

Your AI client, your CRM access

Personal omk_ keys on /api/mcp — Claude, Cursor, and more.

External AI tools should work like you do in Operations — same objects, same field access, same attribution. OSTRATA exposes a hosted MCP server so members connect their own clients without sharing admin REST keys.

Each connection is member-owned and revocable. Keys inherit your current permission profile automatically. Records created via MCP are attributed to you — not a workspace admin fallback.

Personal omk_ keys
Created in Personal space → MCP — separate from admin osk_ REST keys.
Claude-first setup
Copy-ready config for Claude Code, Claude Desktop (secure env pattern), and Cursor.
Pilot-style tools
search_records, CRUD, schema mutations, import, and attachments — not a thin REST mirror.

Personal path

Member path, not admin API

MCP and the admin REST API are independent integration surfaces.

Any workspace member creates connections from Personal space → MCP
omk_ keys authenticate only on /api/mcp
Admin osk_ keys on Setup → API stay on /api/v1 only

Permissions

Permission-bound access

Your MCP connection uses the permission profile assigned to your membership.

Profile changes propagate on the next MCP request
Field and object restrictions match Operations
Import tools require a workspace-admin profile

Secure setup

Secure client configuration

Claude Code uses native HTTP Bearer auth. Claude Desktop uses mcp-remote with tokens in env.

HTTPS required in production
Secrets shown once at creation — revoke if exposed
Use mcp-remote@latest (≥ 0.1.16) for Desktop

Tool catalog

Twenty-two MCP tools cover discovery, records, schema, import, and attachments.

list_objects and describe_object for schema discovery
search_records with structured filters like Pilot
create_record sets created_by to the connection owner

Questions

Short answers before you request access.

Where do I create an MCP connection?: Personal space → MCP. Create a connection, copy the omk_ secret once, then follow the client-specific steps on that page or in the API documentation (MCP section).
Can I use my admin API key for MCP?: No. Admin osk_ keys work only on /api/v1. MCP requires a personal omk_ key from Personal space → MCP.
Which AI client is recommended?: Claude Code — native HTTP transport with Bearer auth, no mcp-remote proxy required.
Who owns records created via MCP?: You do. created_by and updated_by reflect the member who owns the MCP connection.