FFS MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FFS_BASE_URL | Yes | FFS API base URL | |
| FFS_RC_API_URL | Yes | RingCentral API URL | |
| FFS_RC_CLIENT_CREDENTIALS | Yes | Base64 encoded client credentials |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ffs_get_user_infoA | Get AccountId and ExtensionId from RingCentral credentials. Use ExtensionId for individual user, AccountId for entire company. |
| ffs_search_flagC | Search for FFS flags by keyword. Returns matching flags with their IDs and types. |
| ffs_get_flag_optionsC | Get all available options (values) for a Flag. Shows Value IDs needed for updates. |
| ffs_check_accountB | Check the current status of an AccountId or ExtensionId in a Flag. |
| ffs_update_accountC | Update an AccountId or ExtensionId to use a specific Flag value. Uses MCP Auto Condition for management. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: checking account status, getting flag options, retrieving user info, searching flags, and updating accounts. There is no overlap in functionality, and the descriptions make the boundaries explicit, preventing agent misselection.
All tools follow a consistent 'ffs_verb_noun' pattern with snake_case, such as ffs_check_account and ffs_update_account. This predictability makes the tool set easy to navigate and understand at a glance.
With 5 tools, the server is well-scoped for managing FFS flags and accounts. Each tool serves a specific, necessary function without redundancy, fitting typical expectations for a focused utility server.
The tool set covers core CRUD-like operations for FFS management: checking, searching, getting info, and updating. A minor gap exists in not having a tool to create or delete flags, but the available tools support key workflows without dead ends.