Fellix Docs

Integrations

Use Fellix from Cursor

Connect Fellix to Cursor to look up clients, summarize conversations, list or move appointments, and send replies. The assistant acts as you, sees what you see, and can do only what your role and the permissions you approve allow. Any member whose role can grant at least one permission can set it up.

Before you start

Open Fellix and Cursor. You need an account in each and an eligible Fellix organization.

Steps

  1. Add this entry to ~/.cursor/mcp.json for every project, or .cursor/mcp.json for one project: 
    {
  "mcpServers": {
    "fellix": { "url": "https://api.fellix.ai/mcp" }
  }
}
  2. When Cursor offers sign-in, continue in the browser to the Fellix consent page.
  3. Sign in to Fellix. Choose an Organization and review Permissions.
    Fellix consent page showing ChatGPT as the requesting app, an organization selector, and permissions grouped by resource.
    Fellix’s consent page (shown here for ChatGPT; it names your assistant)
  4. Leave the permissions you need ticked, then select Authorize.
    The Authorize and Cancel buttons and connection expiry notice on the Fellix consent page.
    Fellix’s consent page: review the connection duration and select Authorize.

Choosing the organization

Choose the organization on the consent page. Organizations where your role can grant nothing are not listed. Each connection is limited to the organization you select.

Permissions

The consent page groups permissions as Read and Write by resource. The assistant is limited by both your role and the permissions you approve; review the choices before authorizing. The assistant’s own settings determine whether it asks before a write action.

What it can do

Try these requests:

  • “Find the client Maria Lopez and summarize her last conversation.”
  • “List today’s appointments in Fellix.”
  • “Draft a reply to Maria Lopez’s latest conversation.”

Where your assistant shows MCP prompts, these three ready-made prompts appear there:

  • Inbox briefing — What moved in the Fellix inbox lately and what needs a person, without changing anything.
  • Follow up warm leads — Open hot and warm leads that have gone quiet, with a drafted follow-up for each, sent only once you approve.
  • Today's appointments — The day's appointments in the organization's time zone, with what still needs confirming.

What it will not do

No tool charges a card or takes payments. Conversation access is limited to web chat, WhatsApp, Instagram and Messenger through channels your organization has connected. A WhatsApp message cannot be sent when the organization has no WhatsApp channel.

Good to know

  • Everything the assistant sends goes out under your name, as if you had sent it.
  • A connection lasts up to 90 days and ends sooner if unused for 30 days. Connect again when it ends.
  • You can have at most 10 connected apps per person per organization.
  • Each connection is for one organization. To switch, disconnect and connect again, choosing the other organization.
  • The yellow “Fellix has not reviewed this application” note is expected for assistants Fellix has not marked as reviewed.

Disconnecting

In Fellix, open Account Settings → Connected apps, select Disconnect for the connection, and confirm.

The Connected apps page in a Fellix member profile, listing connected applications and their permissions.
Account Settings → Connected apps lists your connections.
A confirmation dialog asks whether to disconnect a connected app.
Confirm Disconnect to end the connection.

The organization owner can disconnect any member’s connection under Settings → API keys → Connected apps.

The organization’s Connected apps list under API keys, showing member connections.
Settings → API keys → Connected apps lists the organization’s connections.

Troubleshooting

  • “Organizations where your role can grant nothing are not listed.” Ask an owner to review your role in the organization.
  • “Your role cannot grant anything in any of your organizations, so there is nothing to connect.” Ask an owner to review your role.
  • “This authorization request is not valid” The application or return address was not recognized. Go back to the assistant and start again.
  • “That authorization could not be completed. Try again.” Return to the assistant and start the connection again.
  • “You already have 10 connected apps in this organization. Disconnect one under Account Settings → Connected apps and try again.” Disconnect a connection you no longer need, then try again.
  • “This refresh token is no longer valid: it was already used, it expired, or the connection was ended. Authorize the connection again.” Start the connection and authorize again.
  • “This credential does not have the [scope] scope.” Disconnect and connect again with the required permission ticked.
  • “Your role in this organization cannot do this in Fellix, so an assistant acting as you cannot either. An owner can change your role.” Ask an owner to review your role.

Reference

See the MCP developer reference for all tools, permissions and protocol details.