Skip to content
Scalekit Docs
Talk to an Engineer Dashboard

Connect AI agents to the Typefully MCP server

Vendor MCP
Open markdown

The Typefully MCP connector routes your AI agent's tool calls to Typefully's own MCP server through Scalekit. Each user signs in to Typefully once, and Scalekit stores and refreshes their tokens, so your agent never handles credentials. It comes with 24 tools.

Tools
24
What they doRead · write · destructive
11 · 4 · 911 read4 write9 destructive
Users sign in with
OAuth app
Your own Typefully MCP server app

Setup

  1. Install the SDK

    Terminal window
    npm install @scalekit-sdk/node dotenv
  2. Set your credentials

    Add your Scalekit credentials to your .env file. Find values in app.scalekit.com > Developers > API Credentials.

    .env
    SCALEKIT_ENVIRONMENT_URL=<your-environment-url>
    SCALEKIT_CLIENT_ID=<your-client-id>
    SCALEKIT_CLIENT_SECRET=<your-client-secret>
  3. Create the Typefully MCP connection

    In AgentKit > Connections, create a Typefully MCP connection and copy its redirect URI. The name you give it is the connection_name your code passes. See Configure connections.

  4. Register an OAuth app

    Typefully MCP server connections use your own OAuth app. Register one with Typefully MCP server and add the redirect URI you copied.

    Then enter the app's Client ID and Client Secret on the Typefully MCP connection.

  5. Authorize a user and make your first call

    quickstart.mts
    import { ScalekitClient } from '@scalekit-sdk/node'
    import 'dotenv/config'
    import { createInterface } from 'node:readline/promises'
    const scalekit = new ScalekitClient(
    process.env.SCALEKIT_ENVIRONMENT_URL,
    process.env.SCALEKIT_CLIENT_ID,
    process.env.SCALEKIT_CLIENT_SECRET,
    )
    const actions = scalekit.actions
    const connector = 'typefullymcp'
    const identifier = 'user_123'
    // Generate an authorization link for the user
    const { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })
    console.log('Authorize Typefully MCP:', link)
    const rl = createInterface({ input: process.stdin, output: process.stdout })
    await rl.question('Press Enter after authorizing...')
    rl.close()
    // Make your first call
    const result = await actions.executeTool({
    connector,
    identifier,
    toolName: 'typefullymcp_get_me',
    toolInput: {},
    })
    console.log(result)
    Terminal window
    npx tsx quickstart.mts

    Each user signs in once. See Authorize a user for the full flow and statuses.

Tools

Pass the exact name to execute_tool
Try in PlaygroundRequest a tool
  • typefullymcp_get_draftRetrieve a specific draft by ID, including its content for all configured platforms, status, and scheduling information.Read-only

    Get draft

    Retrieve a specific draft by ID, including its content for all configured platforms, status, and scheduling information. If the draft has comment threads, the response includes Typefully comment-thread markers in `posts[*].text` and, for X Articles, in `platforms.x_article.content_markdown`. These markers are structural anchor metadata for `GET → modify → PATCH` round-trips; preserve them exactly when editing. For read-only display/export, pass `?exclude_comment_markers=true` to render draft text without markers. Content returned with that flag set should not be PATCHed back unless you intend to resolve or remove comment anchors. **Draft statuses:** 'draft' = saved but not scheduled. 'scheduled' = queued to auto-publish at its scheduled_date. 'planned' = dated but inert: it has a scheduled_date but will NOT auto-publish until confirmed (by setting publish_at). A planned draft whose scheduled_date has passed is NOT overdue and NOT a failure - it simply hasn't been confirmed; replan it or confirm it. 'publishing' = a publish is in flight (transient). 'published' = successfully posted. 'error' = publishing failed. **Required permission:** READ access to this social set.

    Inputs

    draft_idnumberrequired
    No description.
    social_set_idnumberrequired
    No description.
    exclude_comment_markersboolean
    When true, render `posts[*].text` as plain user-visible text without `<typ:comment-thread>` markers, and render X Article `content_markdown` without comment markers. Use only for read-only flows (LLM context windows, exports). The default (false) emits markers so a round-trip back to PATCH preserves comment anchors.default false
  • typefullymcp_get_meRetrieve the currently authenticated Typefully user associated with your API KeyRead-only

    Get current user

    Retrieve the currently authenticated Typefully user associated with your API Key

    Inputs

    This tool takes no inputs.

  • typefullymcp_get_media_statusRetrieves the processing status of an uploaded media file.Read-only

    Get media status

    Retrieves the processing status of an uploaded media file. Poll this endpoint after uploading to check when the file is ready to use in drafts. If no file is received before the upload URL expires (1 hour), the media transitions to 'failed' — create a new media upload and try again. **Required permission:** READ access to the social set.

    Inputs

    media_idstringrequired
    No description.
    social_set_idnumberrequired
    No description.
  • typefullymcp_get_queueRetrieve queue slots and the scheduled AND planned drafts occupying them, between `start_date` and `end_date` (inclusive).Read-only

    Get queue

    Retrieve queue slots and the scheduled AND planned drafts occupying them, between `start_date` and `end_date` (inclusive). Check each draft's `status`: 'scheduled' = will auto-publish at its `scheduled_date`; 'planned' = dated but inert - it will NOT auto-publish until confirmed (a past planned date is not overdue and not a failure). **Required permission:** READ access to this social set. Notes: - `start_date` and `end_date` are interpreted in the social set timezone. - Ranges larger than 62 days are rejected.

    Inputs

    end_datestringrequired
    No description.
    social_set_idnumberrequired
    No description.
    start_datestringrequired
    No description.
  • typefullymcp_get_queue_scheduleRetrieve the queue schedule rules for a social set.Read-only

    Get queue schedule

    Retrieve the queue schedule rules for a social set. **Required permission:** READ access to this social set. Behavior: - If the schedule row does not exist yet, it is created with defaults.

    Inputs

    social_set_idnumberrequired
    No description.
  • typefullymcp_get_social_set_detailsRetrieve detailed information about a social set, including every configured social media platform (X, LinkedIn, Mastodon, Threads, Bluesky) with account details and profile information.Read-only

    Get social set details

    Retrieve detailed information about a social set, including every configured social media platform (X, LinkedIn, Mastodon, Threads, Bluesky) with account details and profile information. **Required permission:** READ access to the social set.

    Inputs

    social_set_idnumberrequired
    No description.
  • typefullymcp_linkedin_resolve_linkedin_organization_from_urlResolve a LinkedIn company/school URL into organization metadata that can be used to build LinkedIn mention syntax in post text.Read-only

    Resolve LinkedIn organization

    Resolve a LinkedIn company/school URL into organization metadata that can be used to build LinkedIn mention syntax in post text. This endpoint is resolver-only and is not a general organization search endpoint. Mention format: `@[Company Name](urn:li:organization:123456)` **Required permission:** READ access to the social set.

    Inputs

    organization_urlstringrequired
    Public LinkedIn organization URL (company or school profile).
    social_set_idnumberrequired
    No description.
  • typefullymcp_list_commentsRetrieve comment threads attached to a draft, ordered by creation time.Read-only

    List comment threads

    Retrieve comment threads attached to a draft, ordered by creation time. Each thread includes the original `selected_text` snapshot and the full ordered list of comments. By default this endpoint returns only unresolved threads (`status=unresolved`). Use `status=resolved` to list resolved threads or `status=all` to list both unresolved and resolved threads. Example: `GET /v2/social-sets/4/drafts/12/comment-threads?status=all&limit=50`. **Required permission:** READ access to this social set.

    Inputs

    draft_idnumberrequired
    No description.
    social_set_idnumberrequired
    No description.
    limitnumber
    No description.default 10
    offsetnumber
    No description.default 0
    platformstring
    Optional platform filter.
    statusstring
    Resolution filter. Defaults to `unresolved`, so resolved threads are omitted unless you request `resolved` or `all`.one of unresolvedresolvedalldefault unresolved