Typefully MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TYPEFULLY_API_KEY | Yes | Your Typefully API key (get it from Settings > Integrations in Typefully) |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_draftA | Create a new draft on Typefully. Supports single tweets and threads. |
| get_scheduled_draftsA | Get recently scheduled drafts from Typefully. |
| get_published_draftsA | Get recently published drafts from Typefully. |
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 3 tools
Each tool targets a distinct operation: creating drafts, retrieving published drafts, and retrieving scheduled drafts. There is no overlap in purpose.
All tool names follow a consistent 'verb_noun' pattern in snake_case: create_draft, get_published_drafts, get_scheduled_drafts.
With 3 tools, the server is minimal but covers core draft creation and retrieval. It is slightly under but reasonable for a focused MCP server.
Missing essential operations like update and delete drafts, which are typical for a content management server. Agents cannot modify or remove drafts once created.