MCP Integrations
Let compatible AI clients call 1MarketingTool workflows from your machine through one local MCP server.
MCP integrations let compatible AI clients use 1MarketingTool's tools locally — useful when you want an AI assistant to check rankings, write a campaign piece, drive a browser capture, or assemble a video without leaving its own terminal.
One Server, Four Tool Groups
The rank, content, video, and browser tools all live behind a single onemarketingtool server. A CLI agent needs one entry in its config rather than four, and setup removes the older separate entries automatically.
| Group | What an agent can do |
|---|---|
| rank | Check a domain's rankings, list snapshots and alerts, run the ranking automation |
| keyword | Keyword overview, exploration, SERP position, terms a domain already ranks for |
| content | Generate a campaign, write a single piece, list the content library, check local AI status |
| video | Write and read a storyboard, add scenes, voiceover and captions, reorder, compose |
| browser | Fetch product info, read a site's brand, list captures, run the Google Webmaster automation |
Why the name has no digit. Some AI clients silently expose no tools at all when a server name begins with a number, which is why the old
1marketingtool-browser-style names were replaced with the letter-prefixedonemarketingtool. Legacy entries are removed on setup. "1mkt", "1marketingtool", and "onemarketingtool" all still work as spoken aliases when you are talking to an agent.
Client Options
Supported clients include Claude Code CLI, Codex CLI, Gemini CLI, OpenCode CLI, Kiro CLI, and Claude Desktop. Enable the clients you actually use.
Configuration
Copy the generated MCP configuration snippet from Settings → MCP Integrations, then add it to the target client following that client's own setup instructions. The app must be running — every tool call proxies to it over a loopback bridge.
Safety
MCP runs locally but still hands powerful actions to an AI client. Enable only the tools you need, and review commands before running workflows that change files, publish content, or submit URLs.
Next
- API Keys and AI CLIs — the agents that connect here
- API Providers — the keys these tools spend