Raims MCP

Raims MCP lets an AI application read data and request operations in the account you authorize. One connection covers the company's permitted environments and the access defined during consent.

https://mcp.raims.com

Signing in to the AI application and signing in to Raims are separate steps. The application does not need your Raims password or a Public API key. The current permissions of the person who authorized the connection continue to limit access.

MCP uses the general Authorized applications authorization flow. The same permission page and list support other compatible applications that connect your account to Raims.

In authenticated applications, search_raims_documentation searches public documentation for instructions and examples, returning excerpts and links. The search does not require a separate permission during consent. Account queries and operations use the access you authorize.

Connect your account

1. Add the MCP URL to the compatible application's settings.
2. Connect and complete sign-in on the Raims page opened in your browser.
3. Under Permissions, check the application and select the operations it can perform. Use a suggested profile or adjust each item.
4. Select Review to check the application, account, environments, return destination and permissions in the summary.
5. Choose Authorize access and complete the security confirmation when requested.
6. Return to the AI application to continue.

Operations are independent and organized by resource, such as Customers, Charges, and Webhooks. Selecting creation does not select queries, updates, revocations, or refunds. Use search to find an operation and Learn more to check its explanation and accepted environments.

Use Back from the review to adjust permissions. Your selection is preserved.

Sign-in keeps the account's security controls, including MFA when requested. If you do not recognize the request or do not want to grant the permissions, close the page without authorizing. Access is granted only after confirmation.

Consent authorizes the connection once. The AI can then run granted operations without opening a Dashboard approval for each task. Current account permissions and the rules for each resource still apply.

If access, permitted environments or account status change while connecting, the page asks you to review the updated account details and access before completing consent. Authorization is not retried automatically.

A compatible application can renew authorization without asking for your password again. If the connection expires, is revoked or cannot be renewed, connect the account again and review consent.

Sandbox and Production use the same URL. A new connection includes all environments permitted for the account and your access, without choosing an environment during consent. The selected permissions apply to those environments. Switching the Dashboard environment does not change the connection's scope. Unavailable environments, resources and permissions remain blocked.

If a connection is limited to one environment, reconnect to authorize the environments currently permitted. Renewing authorization preserves its scope.

Configure your application

With the Raims CLI installed, view the instructions for your client:

raims mcp setup --client codex
raims mcp setup --client claude-code
raims mcp setup --client cursor

The command shows configuration without credentials and does not run the application. --save PATH saves a snippet to a new file; it does not overwrite or merge existing settings. Review the plan with --dry-run.

Codex

codex mcp add raims --url https://mcp.raims.com
codex mcp login raims

Claude Code

claude mcp add --transport http raims https://mcp.raims.com

Then open Claude Code, run /mcp and complete Raims authentication.

Cursor

Add this entry to .cursor/mcp.json or your personal Cursor MCP settings, preserving other servers:

{
  "mcpServers": {
    "raims": {
      "url": "https://mcp.raims.com"
    }
  }
}

Connect the server in Cursor and complete consent in your browser.

Check the account context

Ask the assistant to call get_raims_account_context before guiding an action that depends on your account. The assistant sets data_environment to Sandbox or Production from the authorized environments. The tool reports the company, queried environment, current status, available capabilities and observation time.

The context also describes currency, units and the reference time zone. Financial amounts use integer cents. A receivables forecast is not available balance, and an accepted request does not confirm payment or completion.

Read the context again after an account or access change. Unavailable information must not be treated as zero. Permission to start a request does not replace Raims operation validation.

Run authorized operations

After authorizing the connection, ask the application to perform the actions you want. For example, it can create, update or delete webhooks when those permissions have been granted. You do not need to approve each task on a separate Raims page.

The connection remains limited to the company, authorized environments, granted access and current permissions of the person who authorized it. In each call to raims_api_read, raims_api_write or get_raims_account_context, the assistant sets data_environment to match the request. The result identifies the environment queried or changed. Raims checks limits, balance, eligibility and resource rules for each request.

Before running a request, call raims_api_details: the data_environments field lists the environments the endpoint accepts. The selected environment must be accepted by the endpoint and authorized for the connection. Simulations accept only Sandbox and do not change Production data.

If a write result is uncertain, inspect the resource before requesting another creation. An accepted request does not confirm that a withdrawal reached its destination or that an email was delivered.

Manage and revoke access

In the Dashboard, open Integration, Authorized applications. Members can view their own connections. View company applications includes connections authorized by the owner and team. Revoke team connections also allows viewing them and revoking other employees' connections, but not the owner's. Device permissions do not grant this access. From the actions menu, use Edit permissions to review granted access or Revoke access to end a connection, according to your permissions. Opening the editor does not change access.

Edit permissions lets you remove or restore access from the original authorization, with security confirmation, without changing environments or expiration. See Edit permissions for who can edit access and when a new authorization is required.

Integration keys are under Integration, API keys and require the corresponding permissions.

Signing out of the Dashboard does not replace revoking the application. Use Revoke access to end that authorization.

Revocation prevents new calls authorized by the connection. It does not undo completed operations or erase data already received by the external application. Current account and team-member permissions remain enforced.

Recorded actions performed by an employee through MCP preserve that employee's identity under Account / Activity log. Members see their own activity; View full audit log extends access across the company. The history also shows connection authorizations, permission changes, revocations, and expirations. Automatic events are identified as System.

Resolve connection issues

If a network failure or temporary unavailability prevents the connection request from loading, the page keeps loading and retries automatically while the failure remains temporary. Wait for the result. Only the request lookup is retried; authorizing access still requires your confirmation.

• If the request has expired or is no longer available, return to the application that started the connection and request new access. Reopening the same link does not renew the request.
• If the request lookup is denied, check the account and your current access. An access denial ends automatic retries.
• If the application asks for authentication again, connect and review the consent shown by Raims.
• If an operation is not allowed, check the environment, granted permissions and the operator's current access. The connection does not expand that access.
• If you receive DATA_ENVIRONMENT_NOT_ALLOWED, adjust the request to use one of the environments listed in raims_api_details.data_environments. New authorization does not enable an environment the endpoint does not accept or allow simulations in Production.
• If the account is not the expected one, stop the action and connect the correct account. If the environment is incorrect, adjust the request to the assistant before continuing. An environment outside the connection's scope needs new consent.
• If a request result is uncertain, inspect the resource state before asking for another creation or repeating the action.

Application documentation

• MCP in Codex
• MCP in Claude Code
• MCP in Cursor