Set up Rulebase access

When to use it

Reach for this when someone says any of these — they are the phrases the skill itself triggers on:

• “connect Claude to Rulebase”
• “install the Rulebase MCP”
• “set up the Rulebase connector”
• “create a Rulebase API key”
• “how do I sign up for Rulebase”
• “Rulebase returns 401”
• “no token provided”

How it works

The method, in the order the skill runs it. The full procedure — tables, worked examples and the edge cases — is in the skill itself.

1. The mistake this skill exists to prevent

   Rulebase has two credentials and they are not interchangeable.

2. Step 0: get a workspace

   Rulebase is not self-serve. There is no public sign-up form, and no way to create an organization yourself.

3. Step 1: find the data region

   Everything else depends on this, and it is decided by which host you sign in at — there is no region setting to read, and a user cannot move themselves between regions.

4. Step 2: connect the MCP server

   The endpoint must include the /mcp path. The bare hostname is not an MCP endpoint, and clients fail against it with an unhelpful transport error.

5. Step 3: verify the MCP connection

   Do this before any real work, and do it in this order: get_current_organization, get_workspace_schema.

6. Step 4: create an API key

   Only needed if something is pushing data into Rulebase — conversations from a helpdesk with no native connection, or back-office work items from an internal tool. Reading via MCP needs no key.

7. Step 5: verify the key

   Authenticate with Authorization: Bearer <key>. Listing conversation uploads is the right first call because it only reads.

Related skills

• QA coverage auditSee how much of your conversation volume QA actually covers
• Workspace SQLQuery your workspace without double-counting
• Upload callsPush call recordings into Rulebase in reviewed batches