bird
Server Details
Read SMS, WhatsApp, email, contacts and audiences from your Bird workspace, plus safe CRM writes.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- m190/usefulapi-mcp
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
16 toolsbird_create_audienceCreate an audienceDestructiveInspect
Creates an audience (contact list) in Bird — additive, sends no message. Static audiences start empty. Bird API: POST /v1/audiences.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Display name for the audience. | |
| type | No | How members are determined. Only `static` is generally available. | |
| description | No | Longer description of who this audience is. |
bird_create_contactCreate a contactDestructiveInspect
Creates a contact (CRM record) in Bird — additive, sends no message. Contacts are unique by email. Bird API: POST /v1/contacts.
| Name | Required | Description | Default |
|---|---|---|---|
| data | No | Custom property values. Each key must be a property created via the contact-properties API; values match the property's declared type. | |
| Yes | The contact's email address (unique within the workspace). | ||
| last_name | No | The contact's last name. | |
| first_name | No | The contact's first name. | |
| external_id | No | Your own identifier for this contact (unique within the workspace). |
bird_get_audienceGet an audienceRead-onlyInspect
Fetch a single audience by id. Bird API: GET /v1/audiences/{audience_id}.
| Name | Required | Description | Default |
|---|---|---|---|
| audience_id | Yes | Audience id. |
bird_get_contactGet a contactRead-onlyInspect
Fetch a single contact by id. Bird API: GET /v1/contacts/{contact_id}.
| Name | Required | Description | Default |
|---|---|---|---|
| contact_id | Yes | Contact id. |
bird_get_email_messageGet an email messageRead-onlyInspect
Fetch a single email message by id. Bird API: GET /v1/email/messages/{message_id}.
| Name | Required | Description | Default |
|---|---|---|---|
| message_id | Yes | Email message id. |
bird_get_sms_messageGet an SMS messageRead-onlyInspect
Fetch a single SMS message by id. Bird API: GET /v1/sms/messages/{message_id}.
| Name | Required | Description | Default |
|---|---|---|---|
| message_id | Yes | SMS message id. |
bird_get_whatsapp_messageGet a WhatsApp messageRead-onlyInspect
Fetch a single WhatsApp message by id. Bird API: GET /v1/whatsapp/messages/{message_id}.
| Name | Required | Description | Default |
|---|---|---|---|
| message_id | Yes | WhatsApp message id. |
bird_list_audience_contactsList an audience's contactsRead-onlyInspect
List the contacts that belong to a static audience, as a cursor page. Bird API: GET /v1/audiences/{audience_id}/contacts.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max items per page. | |
| audience_id | Yes | Audience id. | |
| starting_after | No | Cursor from a previous response's `next_cursor` field, to fetch the next page. |
bird_list_audiencesList audiencesRead-onlyInspect
List audiences (contact lists) in the workspace, newest first, as a cursor page. Bird API: GET /v1/audiences.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max items per page. | |
| starting_after | No | Cursor from a previous response's `next_cursor` field, to fetch the next page. |
bird_list_contact_propertiesList contact propertiesRead-onlyInspect
List the custom contact-property definitions (schema) for the workspace. Bird API: GET /v1/contact-properties.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max items per page. | |
| starting_after | No | Cursor from a previous response's `next_cursor` field, to fetch the next page. |
bird_list_contactsList contactsRead-onlyInspect
List contacts (CRM records) in the workspace, newest first, as a cursor page. Bird API: GET /v1/contacts.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max items per page. | |
| starting_after | No | Cursor from a previous response's `next_cursor` field, to fetch the next page. |
bird_list_email_messagesList email messagesRead-onlyInspect
List email messages sent from the workspace, newest first, as a cursor page. Bird API: GET /v1/email/messages.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max items per page. | |
| starting_after | No | Cursor from a previous response's `next_cursor` field, to fetch the next page. |
bird_list_sms_messagesList SMS messagesRead-onlyInspect
List SMS messages (inbound + outbound) for the workspace, newest first, as a cursor page. Bird API: GET /v1/sms/messages.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max items per page. | |
| starting_after | No | Cursor from a previous response's `next_cursor` field, to fetch the next page. |
bird_list_sms_templatesList SMS templatesRead-onlyInspect
List the SMS templates available to the workspace (Bird built-ins + your own). Bird API: GET /v1/sms/templates.
| Name | Required | Description | Default |
|---|---|---|---|
| scope | No | Filter by scope. | |
| category | No | Filter by category. | |
| language | No | Keep only templates in this BCP-47 language tag. |
bird_list_whatsapp_messagesList WhatsApp messagesRead-onlyInspect
List WhatsApp messages (inbound + outbound) for the workspace, newest first, as a cursor page. Bird API: GET /v1/whatsapp/messages.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max items per page. | |
| starting_after | No | Cursor from a previous response's `next_cursor` field, to fetch the next page. |
bird_list_whatsapp_templatesList WhatsApp templatesRead-onlyInspect
List the WhatsApp message templates available to the workspace. Bird API: GET /v1/whatsapp/templates.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!