Beta
The Capsa connector is in beta. It handles a focused set of workflows today, and we're shipping new ones quickly. If Capsa can't do something you need, contact Capsa support. We review every request, and your feedback shapes what we build next.
Setup in Claude
Follow these steps in Claude on the web or desktop app.
- 1
Get access in Capsa
Ask your Capsa super admin to turn on AI connector access for your user.
- 2
Open Claude connectors for your plan
On an individual plan, go to Customize → Connectors, choose +, then Add custom connector. On a Team or Enterprise plan, an owner or primary owner opens Organization settings → Connectors → Add → Custom → Web and continues with the next step. Members wait until Capsa appears under Customize → Connectors, choose Connect, and skip the next step.
- 3
Add Capsa if you are setting it up
Individual users and Team or Enterprise owners: enter https://mcp.capsaintelligence.com as the server URL and name it Capsa if asked. If Claude shows authentication options, keep Sign in now and Use Claude's published identity. Leave the optional OAuth client ID and secret blank. Choose Add. Team and Enterprise owners then return to Customize → Connectors and choose Connect for their own account.
- 4
Sign in and allow access
Sign in with your Capsa account and choose Allow on the Capsa authorization screen.
- 5
Turn Capsa on in a conversation
In a new Claude chat, open + → Connectors and turn on Capsa. If you belong to more than one Capsa organization, choose the organization by name when asked.
- 6
Choose how often Claude asks you
Claude asks you once when Capsa reviews a change and again when it saves the change. A review never changes your records. To approve only the save, open Capsa in Customize → Connectors and set the tools named Preview, Review or Prepare to Always allow. Keep every other Capsa tool set to ask you.
Claude server URL
https://mcp.capsaintelligence.comAlready connected with a manually entered OAuth client ID? That connection can stay in place. Use Claude's published identity for new connections.
Claude's current connector instructionsSetup in ChatGPT
Use ChatGPT on the web. If your workspace controls who can add custom apps, ask a workspace admin to make Capsa available. ChatGPT Pro currently limits custom apps to read-only tools; Business, Enterprise, and Edu workspaces can enable the full set of permitted Capsa tools.
- 1
Get access in Capsa
Ask your Capsa super admin to turn on AI connector access for your user.
- 2
Open the ChatGPT app directory
In ChatGPT on the web, go to Settings → Apps → Browse Directory. If Capsa is already available in your workspace, connect it and skip to the last step.
- 3
Create a Capsa MCP app
Choose Add → Create MCP App. Name it Capsa and paste https://mcp.capsaintelligence.com/mcp into the Connection field. ChatGPT should discover OAuth automatically. If it asks for a registration method, choose Client Identifier Metadata Document (CIMD). Do not enter an OAuth client ID or secret.
- 4
Confirm and create
Select “I understand and want to continue,” then choose Create.
- 5
Ask Capsa what it can do
Start a new chat and ask “@Capsa what can I do with it?” If ChatGPT asks you to connect, sign in with your Capsa account and choose Allow.
ChatGPT Connection URL
https://mcp.capsaintelligence.com/mcpWant your AI to walk you through it?
Paste this into Claude or ChatGPT to ask for help one step at a time.
Help me set up the custom Capsa connector step by step. Use https://capsaintelligence.com/mcp-docs as the guide. If you cannot open the link, ask me to paste the relevant steps. First ask whether I use Claude or ChatGPT and what plan or workspace role I have. Tell me exactly what to click next, wait for me after each step, and help me troubleshoot any screen that looks different.
Updates, next steps and playbooks — in preview
Explore update types, your playbooks and the guidance on each next step, read recent updates, and review outstanding next steps with accountable people and recorded responses. Availability depends on the capabilities shown by your connection. Reading leaves Seen and completion unchanged. With the separate Record update responses permission (an admin turns it on in Users & Permissions), record what you did about a next step (Noted, Contacted customer, Work assigned, or Not actionable with a reason) only after you confirm the exact response, and acknowledge a response as the accountable person. Work assigned names the task or issue the Updates page already created for that next step, or creates one when you also have Create Aspire issues and tasks. Authorized company settings editors can also explain update rules, preview one playbook, guidance or next-step change, and save the exact proposal after your confirmation. Manage updates is a separate connector permission.
Review report groups and Command Center rules — in preview
Explain Sales Groups, Penetration Groups, Profitability Groups, Financial Health, Relationship Health, Property Tier, WIP Job Health rules, Accountability roles, and task and issue types using your Aspire names. Choose free-text subjects, Aspire categories, or your configured work types, with optional free-form exceptions. Accountability roles organize responsibility and primary reporting relationships; they do not grant permissions or change Aspire assignments. Authorized teammates can review a specific change and confirm it before saving. Availability depends on the capabilities shown by your connection.
Manage teammate permissions
Super admins with Manage teammate permissions enabled on their connector can review teammate access, create or edit reusable roles, and apply individually confirmed changes. Capsa shows what access will be gained or lost before saving.
Find proposal follow-ups
Surface outstanding customer follow-up actions with opportunity context, due dates, and customer contact candidates.
Record completed follow-ups
Mark follow-ups complete only after an email provider confirms a send or the user explicitly confirms the follow-up happened.
Find upcoming scheduled visits
Pull scheduled visits with Branch, Account Owner, Division, Service Type, Service, property, and contact context.
Explore Aspire records
With a separate administrator grant, explore current Aspire records and build your own measures across approved relationships. Compare counts, totals, and averages; calculate ratios; or find tickets with no matching visits. Capsa applies your record limits to every related resource and refuses questions it cannot answer within those limits.
Configure Aspire access
Super admins can use Users & Permissions → AI Connector → Aspire access to choose a starter pack or linked roles, limit records by branch or person, and exclude sensitive fields. Review the effective access before saving. Self follows the receiving teammate, including branches they currently manage. Advanced controls support individual resources and fields.
Create Aspire issues and tasks
With separate administrator grants for issues and for tasks, log an issue or a task in Aspire for a property, opportunity, or work ticket you can read. Capsa shows you exactly what will be created and who it is assigned to, waits for your confirmation, then creates it in Aspire and records it in Capsa the same way the app does.
Get property context
Search for properties and pull contact, relationship, production, satisfaction, sales, upcoming-visit, and drilldown context.
Review property health
Compare Financial and Relationship health, complaint evidence, recommendations, and review history. With Update Financial health or Update Relationship health permission, save a change to that status after you confirm it, or apply a current Relationship downgrade allowed by your organization’s automatic rules.
Apply property tiers after review
When available through your connection, review current company tier recommendations or choose Tier A, B or C for selected properties. With the separate Apply property tiers permission and your existing company settings rights, review the exact properties and before-and-after tiers, then confirm each batch of up to 100 properties before saving.
Choose health update modes
When available through your connection, choose Review or Automatic independently for Financial and Relationship health. The separate Change health update modes permission and your existing company settings rights are required. Review the exact choices and effects before confirming. Automatic Relationship health only downgrades; it never upgrades a relationship. Keeping or replacing older Financial assessments is a separate choice shown for your confirmation when needed.
See Business Development deals and prospects
See which Business Development deals need a next step today using the same bands as the Queue, open one deal with its contacts, next steps, captured records, linked opportunities, and stage history, look up the deal and opportunity history of a company, contact, or property, and browse or search prospects.
Update deals and next steps (Write)
With the Update deals and next steps permission, start a deal, change its fields, move it to another stage, mark it lost, or move it to the Aspire pipeline. Capsa shows the exact change, including anything not in Aspire yet, and saves only after you confirm it.
Try these prompts
Start a conversation with Capsa enabled, then ask one of these questions.
Workflow recipes
The Capsa connector provides approved data and action tools. Workflow recipes show agents how to combine Capsa with email, documents, calendars, and user review steps.
Open the Capsa agent cookbookSafe action boundaries
- Task and issue types can be managed through both the app and connector under their own settings permission. Review the selected destination and all required role-based Aspire assignees before creating work. Changes to the rules or role coverage require a fresh review.
- Company settings changes require your existing Capsa editing rights and separate permission for each type of change in AI Connectors. The connector cannot grant itself that access.
- Review the before-and-after explanation before confirming a settings change. Changed or expired previews need a new review. Sales Group renames and removals can update or archive linked sales goals.
- Saving health or tier rules does not apply property tiers or change health update modes. Existing Automatic rules can affect the next evaluation; Review rules change recommendations. After a successful rule save, your agent can offer a separate review of tier application or Automatic health updates. Each action requires its own permission, exact preview and explicit confirmation.
- Apply property tiers and Change health update modes are separate permissions from editing company rules and from updating an individual Financial or Relationship status. Available actions come from your connection’s capability discovery. If an action is unavailable, your agent should say so rather than promise it can save the change.
- Tier changes name the selected properties, with no more than 100 in each reviewed batch. Saved health modes, automatic updates requested and property statuses actually changed are separate outcomes. The agent reports each rule family and action that saved, failed or could not be confirmed; successful saves remain saved when another action fails. These actions do not change personal rules or Aspire records, and do not add WIP tiers.
- Permission management requires an active connector and a separate super-admin permission. If unavailable, check your own access in AI Connectors.
- Page, report and Capsa capability role assignments copy permissions once; later template edits do not change existing teammates. Linked Aspire roles update assigned teammates when published, within their individual record and field limits. Each permission change requires review and confirmation. Manage your own access, other super admins, suspended access, and new invitations in the app.
- Permission previews reflect current app access. If access changes or a preview expires, review a new preview before applying it.
- Independent Aspire access does not grant Pages, Reports or other Capsa capabilities. A hidden field cannot be used in filters, sorting, joins or calculations either. Existing Aspire access and inherited restrictions remain unchanged until an administrator reviews and saves independent access. Saving replaces those inherited restrictions with the Aspire rules shown in the review.
- Reading Aspire records never grants permission to create, update or delete them. Write actions require separate authorization. Independent Aspire rules are edited manually in the app today; AI-assisted rule authoring is planned for a later phase.
- Custom Aspire measures use the fields you choose. Existing Capsa reports remain the reference for named business metrics. A missing or zero denominator returns no ratio; Capsa does not invent a value.
- During the beta, you add Capsa to Claude as a custom connector.
- Capsa does not send email. Use a connected email provider after review and confirmation.
- Capsa data may be up to 24 hours old, so same-day operational decisions should be verified.
- Your Capsa administrator controls which connector capabilities are available to each teammate.
- Related-record queries enforce access on every resource. A no-matching-record question is supported only when Capsa can verify complete visibility for that relationship. The current visit record has no visit status field, so Capsa will not infer one.
- Your administrator chooses which kinds of Aspire records each teammate can explore, and grants creating issues and creating tasks separately. A record is created only after you confirm the exact issue or task, including its assignee; a confirmation lasts 30 minutes, and sending the same confirmation again never creates a duplicate.
- Completion is never recorded just because a draft was created.
- Financial and Relationship health changes each need their own permission. The connector changes a status only after you confirm the property and the change, or for a Relationship downgrade your organization’s automatic rules support. It never upgrades Relationship health on its own and never changes health in Aspire.
- Branch limits on Aspire activities, companies and contacts follow their associated properties: a record needs at least one property in an allowed branch. Unlinked records are hidden, and shared records do not reveal other-branch properties. An administrator must review and save access to these resources.
- Under Capsa capabilities, Set branches once applies a reviewed branch selection to Follow-up actions, Upcoming visits, Property context and Renewal opportunities. Their property and follow-up writes inherit those limits. Business Development and company settings remain company-wide; Aspire access is managed separately.
- Property health is limited to the Branches and Account Owners your administrator allows in the connector and the properties you can access in Command Center.
- Updates use the same property access and connector Branch and Account Owner limits. Recent-feed windows never expire outstanding next steps. Update setup tools manage company rules, individual playbooks, next-step lines and their guidance, starting dates and your hidden-playbook view through reviewed proposals and explicit confirmation. Shared changes require company settings rights and the separate Manage updates connector permission. Next steps already recorded keep their due day and accountable person; guidance changes show on open next steps right away.
- Recording a response or an acknowledgment requires the separate Record update responses permission and your explicit confirmation of the exact response. Reading an update or drafting a message never counts as a response, Not actionable needs a reason, and adding the note to Aspire needs the Add notes to Aspire permission. Work assigned names the task or issue already created for that next step, or creates one after you confirm its details when you also have Create Aspire issues and tasks. Apart from that task or issue, responses never create tasks, and they never message your customers.
- Business Development shows the whole company’s deals, exactly as the app does. Branch, Sales Rep, and Account Owner limits set for other capabilities do not apply to it, and your administrator controls its connector read access independently of app page access. Deal changes require a separate Write permission.
- Deal changes are saved in Capsa only and never change Aspire records. Each change is shown for review and saved only after you confirm it. Deleting deals is not available through the connector, and a deal’s main contact and captured company name can only be set when it is created.
Need access?
Capsa connector access is managed inside the Capsa app by your Capsa super admin. Ask your super admin to open Administration, then Users & Permissions, and enable AI Connector access for your user. Then open Resources → AI Connections → Setup and usage guide. Connector-enabled teammates can open Resources → AI Connector Docs directly.