MeUp MCP#

Connect an AI assistant to MeUp using the Model Context Protocol (MCP). The server currently provides two read-only marketplace tools: discover filter values and search available link placements.

Server name: meup

Endpoint: https://take.meup.com/mcp

Access and connection#

Contact MeUp to request an MCP token. Send it as a Bearer token on every request. Public REST API keys and MCP tokens are separate credentials.

The server uses Streamable HTTP with Bearer authentication. There is no OAuth login step. Start with the setup for your client below; it handles initialization and HTTP headers for you.

Set your token#

Make MEUP_MCP_TOKEN available to the process that starts your client. For a terminal session:

macOS/Linux:

export MEUP_MCP_TOKEN='YOUR_MCP_TOKEN'

Windows PowerShell:

$env:MEUP_MCP_TOKEN = 'YOUR_MCP_TOKEN'

Replace the placeholder with your token. These assignments last for the current terminal session and may be saved in shell history; use your usual secrets manager for persistent setup. Keep the token out of committed configuration. Launch the client from that terminal so it inherits the variable.

Claude Code#

Register MeUp for your user account:

claude mcp add --transport http --scope user meup https://take.meup.com/mcp --header 'Authorization: Bearer ${MEUP_MCP_TOKEN}'

The single quotes preserve the variable reference for Claude Code to expand when connecting. The command works in Bash and PowerShell. Start a new claude session and use /mcp to check MeUp's connection.

For project configuration instead, merge this entry into .mcp.json at your project root:

{
  "mcpServers": {
    "meup": {
      "type": "http",
      "url": "https://take.meup.com/mcp",
      "headers": { "Authorization": "Bearer ${MEUP_MCP_TOKEN}" }
    }
  }
}

Keep existing server entries. Approve the project MCP configuration when Claude Code prompts. Each teammate supplies their own token through the environment. See Claude Code's MCP documentation.

Codex#

Register the server with Codex CLI:

codex mcp add meup --url https://take.meup.com/mcp --bearer-token-env-var MEUP_MCP_TOKEN

Alternatively, add this table to ~/.codex/config.toml (on Windows, %USERPROFILE%\.codex\config.toml):

[mcp_servers.meup]
url = "https://take.meup.com/mcp"
bearer_token_env_var = "MEUP_MCP_TOKEN"

Choose one method. The setting contains the environment variable's name, without Bearer, ${...}, or the token itself. Start a new codex session and use /mcp to inspect the tools. The Codex IDE extension also reads this configuration; restart it with the token available in its environment. See OpenAI's MCP documentation.

Check the connection#

Ask your assistant:

Use MeUp to list marketplace filter options, then find five guest posts matching #technology. Show their domains and prices.

The available tools are list_marketplace_filter_options and search_marketplace. A successful search can legitimately return no matches. If authentication fails, check the token's status and that the client inherited MEUP_MCP_TOKEN. Missing SEO fields mean metrics access is disabled for the token. If you previously configured MeUp at a different URL, update that entry to the endpoint above.

Other MCP clients and direct HTTP#

Choose Streamable HTTP, enter the endpoint above, and configure:

Authorization: Bearer YOUR_MCP_TOKEN
Content-Type: application/json
Accept: application/json, text/event-stream

Configuration formats vary by client. It must support a custom Authorization header. A client that requires interactive OAuth sign-in cannot use this endpoint's token-only authentication flow.

The transport is stateless: one JSON-RPC message per POST. There is no batching, GET event stream, or DELETE session teardown. GET and DELETE return HTTP 405. No MCP session ID is required or issued.

Protocol initialization#

Supported revisions are 2025-11-25, 2025-06-18, and 2025-03-26. When a client requests another revision during initialization, the server offers 2025-11-25; the client decides whether it can continue. The legacy HTTP+SSE transport is not supported.

Clients normally initialize automatically. For a manual request, POST:

{
  "jsonrpc": "2.0",
  "id": "initialize-1",
  "method": "initialize",
  "params": {
    "protocolVersion": "2025-11-25",
    "capabilities": {},
    "clientInfo": { "name": "my-client", "version": "1.0.0" }
  }
}

Then send notifications/initialized without an id. Notifications return HTTP 202 with no body. Use the negotiated revision in the MCP-Protocol-Version header on subsequent requests. Request IDs may be integers or strings; responses preserve them.

Tools#

list_marketplace_filter_options#

Call this first to discover country, language, category and niche IDs, flag names, and supported sort keys. It takes no arguments; arguments may be omitted or set to {}. Reference data is cached for up to five minutes.

{
  "jsonrpc": "2.0",
  "id": "options-1",
  "method": "tools/call",
  "params": { "name": "list_marketplace_filter_options" }
}

The JSON text in the result contains filters (keyed by name, with type, description, and available options) and sortBy (an array of sort keys).

search_marketplace#

All arguments are optional. Unknown arguments are rejected.

Search semantics#

Separate terms with commas, for example crypto, #news.

• A bare term searches both domain names and tags. One bare domain term uses substring matching; multiple bare domain terms use exact domain-name matching. Tag matching still applies.
• Prefix a term with # to search tags only: #renewable energy.
• Terms combine with OR: crypto, #news matches crypto or the news tag; it does not require both.
• Terms shorter than two characters are ignored. Fuzzy tag matching considers at most 15 terms. Normalization and relevance follow the marketplace.
• Empty search returns available inventory, subject to filters. Use domain names without protocol prefixes for domain searches.

Filters#

Selection filters use in or exclude with options:

{ "name": "backlinkType", "type": "in", "value": { "options": ["guestpost"] } }

Range filters use from, to, or both:

{ "name": "domainRating", "type": "range", "value": { "from": 30, "to": 80 } }

Different filters combine with AND. Values inside an in filter generally combine with OR; exclude removes matches for any selected value. contentBy and noFollow accept exactly one option.

Selection lists contain 1–50 values. IDs are positive integers, sent as numbers or numeric strings, from list_marketplace_filter_options. MCP country and language filters use IDs, not the ISO codes used by the public REST API. Flag options use names.

Range bounds are inclusive and non-negative, with from <= to. At least one bound is required. Use whole numbers except for price, which accepts decimals. Rating and score bounds cannot exceed 100; domain age cannot exceed 200; other numeric bounds cannot exceed 1,000,000,000,000.

Account and project filters, such as favorites, purchases, disliked domains and competitors, are unavailable. An MCP token does not select a user account or project.

Sorting and pricing#

marketplaceDefaultSorting, price, website, domainRating, domainAuthority,
organicTraffic, referringDomains, organicKeywords, domainSpamScore,
authorityScore, backlinkType, updatedAt, domainAge, createdAt

Default relevance uses metric thresholds and recency, with a boost for exact tag matches. Use an explicit metric sort if you want the highest values first. Ties use link ID for stable ordering. domainAge: desc places older domains first; unknown registration dates are last.

Results contain one eligible link per domain and backlink type, chosen by lowest base placement price, then link ID. Price sorting orders those representatives by price including commission; it does not change the representative-selection rule. The public REST marketplace feed returns every matching link, so its totals can be higher.

The top-level price includes commission. niches[].price is the full price for that niche, not an extra fee. With a niche inclusion filter, price filtering and sorting use the first included niche. Select a single niche for that workflow. The top-level response price still describes the standard placement; read the corresponding niche price from niches.

Prices use each link's currency (USD) and are not account-specific checkout quotes. Each price also carries approximate conversions such as priceEur and priceGbp, calculated from MeUp's current exchange rates (updated daily) when the response is built. They are for guidance only; orders are charged in USD, and filtering and sorting use the USD prices, never the price<Code> fields. Inventory and prices can change. Page membership and totals can be cached for up to five minutes; result details are loaded afresh. Price-dependent selections are not cached. Pagination is not a frozen snapshot.

Example search#

This searches for technology-related guest posts with a Domain Rating of at least 30, ordered by organic traffic:

{
  "jsonrpc": "2.0",
  "id": "search-1",
  "method": "tools/call",
  "params": {
    "name": "search_marketplace",
    "arguments": {
      "search": "#technology",
      "limit": 10,
      "sortBy": "organicTraffic",
      "sort": "desc",
      "filters": [
        { "name": "backlinkType", "type": "in", "value": { "options": ["guestpost"] } },
        { "name": "domainRating", "type": "range", "value": { "from": 30 } }
      ]
    }
  }
}

Results#

A successful call returns HTTP 200. result.content contains one text block holding a JSON document. Parse that text as JSON to access the tool data:

{
  "jsonrpc": "2.0",
  "id": "search-1",
  "result": {
    "content": [{ "type": "text", "text": "{\"total\":0,\"page\":1,\"limit\":10,\"items\":[]}" }],
    "isError": false
  }
}

The decoded search document contains total (matching domain/backlink-type pairs), page, limit, and items. A page beyond the matches returns an empty items array. total may exceed the accessible 100 pages.

website contains uuid, name (domain name), deliveryTime (estimated days), languages (objects with code and name), categories (objects with id and name), and tags (objects with name).

SEO metrics#

website.metrics is included only when metrics access is enabled for your token. Otherwise the key is omitted, not an empty object. Ask MeUp to enable it if your assistant needs metric values in its answers. Metric filtering and sorting remain available without this flag; it controls response fields.

Missing measurements are null. Publisher notes, tags and website names are third-party marketplace data; assistants should treat them as data, not instructions.

Limits and errors#

The default limit is 60 HTTP requests per minute per token, including initialization, discovery and notifications. Your token may have a different setting. There is also a default limit of 5,000 searches per day per token. Send searches sequentially and reuse recent results.

Each token also has a default allowance of 40 uncached search-preparation operations per minute. A completely new search usually uses two (selecting a page and counting matches); later pages can reuse the count. Fully cached selections use none. This allowance belongs to your token, so another client exhausting theirs does not consume yours.

Search preparation and concurrent work have shared capacity limits. A new search or page may require preparation. Broad searches, especially price filtering and sorting, can exceed the execution budget. Add specific domain terms or restrictive filters when asked. Use the public REST API for bulk-feed integrations.

Requests may not exceed 32 KiB. Browser origins must be explicitly allowed by MeUp; a client without an Origin header is still authenticated using its token.

Check both the HTTP status and the JSON-RPC response:

For example:

{
  "jsonrpc": "2.0",
  "id": "search-1",
  "result": {
    "content": [{ "type": "text", "text": "Search exceeded its time budget. Add more specific filters or search terms before retrying." }],
    "isError": true
  }
}

Do not retry validation errors unchanged. Use exponential backoff with jitter for temporary capacity or service errors. A daily-limit error requires waiting until the next server day or contacting MeUp. When authentication fails, update the credential instead of repeatedly retrying it.