Cirra AI Salesforce Admin MCP Server for Claude

Overview

Cirra AI provides a commercial Model Context Protocol server for Salesforce administration. After OAuth connects your org, MCP clients such as Claude Desktop, Claude Code, ChatGPT, and Cursor can create and manage objects, fields, page layouts, permission sets, flows, validation rules, Apex, and SOQL queries through conversation.

The server is listed in the official MCP Registry as ai.cirra/salesforce-mcp with endpoint https://mcp.cirra.ai/sfdc/mcp. Cirra also publishes admin skills at skills.cirra.ai for deeper Apex, Flow, and audit workflows.

Features

• Custom object and field creation with page layouts and record types.
• Permission set, profile, and field-level security management.
• Flow, validation rule, and approval process configuration.
• Apex class and trigger authoring with SOQL and data inspection.
• OAuth authentication scoped to the connected Salesforce user.
• Support for multiple orgs including sandboxes, scratch orgs, and production.

Use Cases

• Create a custom object with fields and a page layout from a plain-English spec.
• Audit who has access to a sensitive field or permission set.
• Draft a record-triggered flow for case routing with best-practice guidance.
• Run SOQL to inspect data before a metadata change.
• Generate documentation after a multi-step admin update.

Installation

Cirra account setup

1. Sign up at cirra.ai and start the free plan if needed.
2. Authorize your Salesforce org through standard Salesforce OAuth.
3. Copy the MCP URL from the Cirra dashboard.

Claude (Connectors)

1. Add a custom connector under Settings → Connectors.
2. Enter https://mcp.cirra.ai/sfdc/mcp.
3. Complete OAuth when prompted and enable the connector.

Claude Code

claude mcp add --transport http cirra https://mcp.cirra.ai/sfdc/mcp
claude mcp list

Configuration

{
  "mcpServers": {
    "cirra": {
      "url": "https://mcp.cirra.ai/sfdc/mcp",
      "type": "http"
    }
  }
}

Authentication is handled through Cirra and Salesforce OAuth during connector setup, not via static API keys in the JSON config.

Examples

Create a custom object

Create a custom object called Project Milestone with fields for due date, owner, and status, then add it to the default page layout.

Permission audit

Who currently has edit access to the Account.BillingAddress field?

Flow assistance

Build a record-triggered flow that assigns new Cases to the correct queue based on priority.

Security

• Cirra can only perform actions your connected Salesforce user is allowed to perform in Setup.
• Use sandbox orgs for experimentation before applying changes to production.
• Revoke Cirra OAuth access from Salesforce Setup if a connector is compromised.

Troubleshooting

OAuth or connector errors

Re-authorize the org from the Cirra dashboard and confirm the Salesforce user still has API access.

Metadata deploy failures

Check validation errors in the tool response; field types, dependencies, and managed-package constraints may block changes.

Unexpected permission denials

The connected user may lack Modify All Data or object-level permissions required for the requested admin task.

Credits exhausted

Free plans include monthly credits; upgrade or wait for the next billing cycle if tool calls are rate-limited.