Skip to main content
Felan can discover and use tools from customer-selected remote Model Context Protocol (MCP) servers. Remote MCP is available on Trial and Team plans.
MCP tools are not automatically read-only. A tool may change external data according to the permissions you grant during authorization. Review the server and use the least-privilege provider account available.

​
Requirements

The server must:
  • have an https:// MCP endpoint;
  • be compatible with Felan’s mcp-generic Nango provider.

​
Connect a server

1

Open MCP (OAuth)

As an active team member, open Integrations, find MCP (OAuth), and choose Configure.
2

Add the endpoint

Enter a unique name and the server’s HTTPS MCP endpoint, then choose Add and authorize. A team can configure up to 32 active server entries.
3

Authorize with Nango

Complete the provider authorization window. Nango manages the OAuth tokens; Felan does not store them in team configuration or agent workspaces.
4

Start a fresh session

Start a new root session to load the updated server catalog. Its tools are then available to the root agent and delegated subagents.
Any active team member can add, edit, authorize, reauthorize, log out, or remove a server.

​
Status and freshness

  • Connected means Nango has an active authorization.
  • Not connected means a team member must authorize the server.
  • Retry available means authorization failed and can be retried.
Adding or editing a server applies to new sessions. Existing sessions retain their starting catalog. Logging out or removing a server blocks later MCP requests, including from retained sessions; a request already in progress may finish. If a tool is unavailable, confirm the team plan, connection status, endpoint OAuth compatibility, and provider permissions. One unavailable server does not disable ordinary Felan work or other configured MCP servers.