Adextract MCP vs Tin
A side-by-side look at the Adextract MCP and Tin MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Adextract MCP for marketing work over a hosted endpoint; choose Tin for marketing over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Adextract MCP when
- You need dedicated capabilities in the Marketing domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
search_meta_ads, search_meta_pages, get_meta_page_info.
Choose Tin when
- You need dedicated capabilities in the Marketing domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 49/100 · Fair | 45/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 264 |
| Directory activity | 3 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 13 | Not listed |
| Full listing | View Adextract MCP | View Tin |
Tools & capabilities
Adextract MCP tools 13
search_meta_adsSearch Facebook & Instagram adssearch_meta_pagesDiscover pages and location IDsget_meta_page_infoPage transparency and metadataget_meta_ad_detailsEU/UK ad transparency detailssearch_google_adsGoogle Ads Transparency Centersearch_google_ads_advertisersAdvertiser and domain searchget_google_ad_detailsCreative detailsget_google_ads_advertiser_infoAdvertiser profile from Search adssearch_linkedin_adsLinkedIn Ad Librarysearch_tiktok_adsTikTok Ads Librarysearch_tiktok_advertisersTikTok advertiser discoveryget_tiktok_ad_detailsTargeting and creative details- +1 more on the listing page
Tin tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Adextract MCP
{
"mcpServers": {
"adextract-mcp": {
"url": "https://mcp.adextract.co/mcp"
}
}
}
Tin
{
"mcpServers": {
"tin": {
"url": "https://app.tin.computer/mcp"
}
}
}
Frequently asked questions
Adextract MCP is categorized under Marketing and uses a remote HTTP/SSE transport. Tin belongs to Marketing and uses a remote HTTP/SSE transport. Pick Adextract MCP for marketing work and Tin for marketing.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Adextract MCP has no declared pricing — check the project's own site. Tin has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add adextract-mcp and tin as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Adextract MCP has a quality signal of 49/100 (Fair) with 3 views, 0 installs and 0 GitHub stars. Tin has 45/100 (Fair) with 1 views, 0 installs and 264 GitHub stars.