The Megomi API is available as a Model Context Protocol (MCP) server. Connect it once and your AI agent can look up public TikTok, Instagram, Threads, YouTube and LinkedIn data on its own: “audit this creator”, “compare these five videos”, “pull the comments on this post”.
Connect
Section titled “Connect”The server is at https://api.megomi.my.id/mcp. You can connect two ways. Signing in is the one to use if your client supports it: you give the client the URL, it opens a Megomi page, you click Allow, and it gets a key of its own. No secret is pasted anywhere. With an API key, you create the key yourself and send it in a header.
Sign in with your browser
Section titled “Sign in with your browser”claude mcp add --transport http megomi https://api.megomi.my.id/mcpThen type /mcp in a Claude Code session, pick megomi and choose Authenticate.
Add a custom connector and give it https://api.megomi.my.id/mcp. The app finds the sign-in on its own.
{ "mcpServers": { "megomi": { "url": "https://api.megomi.my.id/mcp" } }}(.cursor/mcp.json, or .vscode/mcp.json with servers in place of mcpServers.)
The first time, your client opens app.megomi.my.id, asks you to sign in if you are not, and shows what the app is asking for. Your account needs at least one API key already, so create one on the API Keys page first if you have not.
Allowing an app creates a key named MCP: <app name> on your API Keys page. It spends your credits like any key, so you can set a credit limit on it or revoke it there, and the app loses access within seconds. The key renews itself in the background; if the app is unused for 30 days, it asks you to sign in again.
With an API key
Section titled “With an API key”Create a key on the API Keys page of app.megomi.my.id and send it in the x-api-key header (or as Authorization: Bearer <key>). The same page shows these snippets with your key filled in.
{ "mcpServers": { "megomi": { "url": "https://api.megomi.my.id/mcp", "headers": { "x-api-key": "YOUR_API_KEY" } } }}claude mcp add --transport http megomi https://api.megomi.my.id/mcp \ --header "x-api-key: YOUR_API_KEY"Any client that supports the Streamable HTTP transport works. Give it the URL above and the x-api-key header.
There is one tool per lookup, named after its endpoint: tiktok_video, tiktok_profile, tiktok_comments, instagram_post, threads_profile, youtube_video, youtube_channel_videos, youtube_transcript, linkedin_profile, linkedin_post, tiktok_audience and so on. get_credit_balance returns your remaining credit.
The list follows the endpoints that are switched on, so it can be shorter than the full API reference. A tool’s description is its endpoint’s description, so the agent sees what it returns and what it costs before it calls it. Nothing that buys credit, creates keys or manages an account is available through MCP.
Results and errors
Section titled “Results and errors”A successful call returns the API’s JSON response. An unsuccessful one returns an error that starts with the HTTP status, for example HTTP 402: …. The status codes mean the same here as over REST, and errors that are never charged (429, 503) are never charged here either.
A response larger than 1 MiB is returned as an error that asks the agent to request less, for example with the trim option or a smaller page, rather than cut off.
Good to know
Section titled “Good to know”- Lookups cost credit. The tools are not marked read-only, so a client that asks before running non-read-only tools will ask before a lookup. Checking the balance is read-only.
- An agent in a loop can spend a lot. Set a credit limit on the key you give an agent, or on the key an app created when you allowed it, on the API keys page, to cap it.
- Results are shared with the REST API. A lookup your key already paid for is free to repeat within the cache window, whichever way you ask for it.
- Lookups can take up to a minute. The API waits up to 45 seconds for a result, and some lookups take longer.