Adyntel MCP server
Instructions on how to use the adyntel MCP server
Integrating Adyntel MCP Server with Your Workflows
This guide explains how to connect the Adyntel MCP server to various AI assistants and workflows, enabling you to search and analyze advertising data from Facebook, Google, and LinkedIn directly through conversational AI.
Overview
The Adyntel MCP server implements the Model Context Protocol (MCP) to expose our endpoints to AI assistants. Once connected, you can ask your AI assistant to search for competitor ads, analyze creative strategies, and gather advertising insights across platforms.
Available Tools
search_facebook_ads
Search Meta/Facebook ads by company page or domain
search_google_ads
Search Google Ads by company domain
search_linkedin_ads
Search LinkedIn sponsored content by company page or domain
Prerequisites
Before integrating, you'll need:
Adyntel API credentials - Your email and API key from Adyntel
Integration Methods
Claude Desktop
Add the following to your Claude Desktop configuration file:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json
Replace YOUR_EMAIL and YOUR_API_KEY with your Adyntel credentials.
Important: If your email contains special characters like +, you must URL-encode them. For example:
After saving, restart Claude Desktop. The Adyntel tools will appear in the tools menu.
Cursor
Add the MCP server to your Cursor settings:
Open Cursor Settings (
Cmd+,on macOS,Ctrl+,on Windows)Navigate to Features → MCP Servers
Click Add Server and configure:
Claude Code (CLI)
Add the MCP server using the Claude Code CLI:
This will add the server to your user config at ~/.claude.json. You can also specify a scope:
--scope user(default) - Available in all your projects--scope project- Stored in.mcp.jsonat project root, shared with team--scope local- Private to you, stored in project's.claude.json
Alternatively, manually add to ~/.claude.json:
Verify the connection with:
Other MCP Clients
Any MCP-compatible client can connect using the SSE transport:
Endpoint:
https://mcp.adyntel.com/sse?email=YOUR_EMAIL&api_key=YOUR_API_KEYProtocol: MCP v2024-11-05
Transport: SSE (Server-Sent Events)
Alternatively, you can pass credentials via HTTP headers:
X-Adyntel-Email: Your Adyntel account emailX-Adyntel-Api-Key: Your Adyntel API key
Using the Tools
Once connected, you can interact with the tools through natural language. Your credentials are automatically included from the connection URL, so you don't need to mention them in your prompts.
Example Workflows
Competitor Analysis
Ad Creative Research
Multi-Platform Overview
Handling Pagination
For companies with many ads, results are paginated. The response includes a continuation_token that you can use to fetch more results:
Error Handling
Authentication failed
Invalid email or API key
Verify your Adyntel credentials
Insufficient credits
API credits depleted
Top up your Adyntel account
Validation error
Invalid parameters
Check parameter format and requirements
Request timeout
Slow response from API
Try again or reduce scope of request
Security Considerations
Credentials: Your API credentials are stored in your MCP client configuration. Never share your configuration file or commit it to version control.
Access control: Use your credentials only in trusted environments.
URL parameters: Credentials in the URL may be logged by some clients. Consider using HTTP headers (
X-Adyntel-Email,X-Adyntel-Api-Key) if your client supports them.
Troubleshooting
Connection Issues
Verify the server is accessible at
https://mcp.adyntel.com/sseEnsure your client supports SSE transport
Check for network or firewall restrictions
Tool Not Appearing
Restart your AI client after configuration changes
Verify JSON syntax in configuration file
Check client logs for connection errors
API Errors
Verify your Adyntel credentials are active
Check your API credit balance
Ensure required parameters are provided
Authentication Failed (401 Error)
If you're getting authentication errors despite having correct credentials:
Check URL encoding - Special characters in your email must be URL-encoded:
+→%2B@→%40(though@usually works without encoding)&→%26
Example: If your email is
[email protected], use:
Support
Adyntel API: Contact [email protected]
Last updated