Feather MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| search_leadsB | Search for potential leads by keywords, groups, or interests. |
| send_friend_requestB | Send a friend request with an optional note. |
| get_request_statusA | Check the status of sent friend requests. |
| get_connector_statsC | Get overall Feather Connector statistics. |
| list_contactsC | List Feather Messenger CRM contacts. |
| add_labelB | Add a label to a Feather CRM contact. |
| add_tagB | Add a tag to a Feather CRM contact. |
| send_broadcastB | Send a broadcast message to labeled contacts. |
| get_crm_statsB | Get aggregate Feather CRM statistics. |
| get_growth_metricsB | Get growth metrics over time. |
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 10 tools
The tools mostly map to distinct actions, but add_label and add_tag have overlapping purposes with similar descriptions. The three stats tools (get_connector_stats, get_crm_stats, get_growth_metrics) could also be confused, though their scopes differ.
All tool names follow a consistent verb_noun pattern using snake_case. Verbs and nouns are clear and predictable, making the toolset easy to navigate.
10 tools is a well-scoped size for a CRM/lead-generation server. Each tool serves a clear function without excessive redundancy.
The core lead-to-broadcast workflow is covered, but there are notable gaps: no way to remove labels/tags, update contacts, or cancel friend requests. This can create dead ends for agents managing contacts.