← Registry

Marketing

uptake.me

Provides access to upTake project metrics, weekly overviews, data slices, and social media post drafts, schedules, and publication status.

1 endpoint16 known toolsFirst detected November 3, 2026Last detected November 3, 2026

ENDPOINT 1

https://uptake.me/api/mcp

No auth detected

MCP server metadata

Name
uptake
Version
1.0.0
Capabilities
tools
Server instructions

upTake measures which posts, links and releases bring visits, signups and revenue to the maker's product. One connection opens all the maker's projects: when they have several, call uptake_projects and pass `project` to every tool. Read uptake_overview first. Only quote numbers returned by these tools. Writing tools prepare things in upTake; nothing is ever published or scheduled from here: tell the maker to review and send posts from upTake.

Known tools 16

uptake_projects

The maker's projects (id, name, site).

Inferred read-only
uptake_overview

The project at a glance: product, stage and goal, this week's visits, signups, paying customers and revenue against the 4 previous weeks, top sources over 30 days, last actions and what they brought, this week's moves, the next communication moment, the last weekly report.

Inferred read-only
uptake_data

One slice of project data, when the overview is not enough.

Inferred read-only
uptake_posts

Posts prepared in upTake's Write studio, with their state (Draft, Planned, Scheduled, Published…), networks and link to open them.

Potential side effects
uptake_post

The current version of a post for each of its networks, with whether it is posted.

Potential side effects
uptake_write_post

Prepares a post in upTake's Write studio, in the maker's voice and with tracked links, and returns the text for each network.

Potential side effects
uptake_create_link

Creates a tracked link that tells upTake which visits, signups and payments came from where it is shared.

Inferred read-only
uptake_log_action

Adds an action the maker did outside upTake (a post, a newsletter, a talk) to the journal, so upTake measures what it brought.

Potential side effects
uptake_calendar

One week of the calendar: what was published and what it brought, scheduled posts, posts planned for a day (editorial date), and what is left to plan (moments, this week's moves, ideas).

Inferred read-only
uptake_ideas

Open post ideas (title, angle, network).

Potential side effects
uptake_more_ideas

Asks upTake for a new series of post ideas from the project's data.

Potential side effects
uptake_dismiss_idea

Removes an idea that does not fit, with a reason; upTake will not suggest it again.

Inferred read-only
uptake_update_move

Marks one of this week's moves as done (or reopens it), edits its title or reason, or dismisses it with a reason.

Inferred read-only
uptake_add_move

Adds a move of the maker's own to this week's list.

Inferred read-only
uptake_plan_post

Sets or clears the day a post is planned for in the calendar.

Potential side effects
uptake_link_post_move

Makes a post count for an open move of this week: publishing the post completes the move.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.uptake]
url = "https://uptake.me/api/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "uptake": {
      "type": "http",
      "url": "https://uptake.me/api/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: uptake
Remote MCP URL: https://uptake.me/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "uptake": {
      "url": "https://uptake.me/api/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "uptake": {
      "type": "http",
      "url": "https://uptake.me/api/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "uptake",
  "transport": "streamable-http",
  "url": "https://uptake.me/api/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.