API Keys and AI CLIs
Connect hosted providers, local AI CLIs, and MCP integrations without sending your workspace data to a 1MarketingTool cloud.
1MarketingTool is BYOK. You decide which providers to connect, and the app uses your own API keys or local AI CLIs.
Supported AI CLIs
The app drives local AI command-line tools you already have installed. Each is detected on your machine; enable only the ones you actually use.
| CLI | Image generation |
|---|---|
| Claude Code | No |
| Codex | Yes |
| Gemini | Yes |
Antigravity (agy) | Yes |
| OpenCode | No |
| Amp | No |
| Qwen | Yes |
| Hermes Agent | No |
| Aider | No |
| Grok | No |
Pick the CLI and its model in the AI CLI picker in the top bar. You can also install the SEO agent skills into any of them.
Only Codex, Gemini, Qwen and Antigravity ship a first-party image model, so only those can run Image Generation on the Local AI route. Choosing one of the others there is refused up front with the reason.
A local CLI has no web retrieval. Where that matters — such as AI Visibility trackers — its answers are labelled as model memory rather than a live citation.
Kiro CLI and Claude Desktop are MCP clients, not AI CLIs the app drives. You install 1MarketingTool's MCP server into them; see MCP Integrations.
Hosted Providers
Use hosted providers when a workflow needs external data or a model you prefer:
- OpenAI, Claude, Gemini, or another AI provider for generation.
- DataForSEO for keyword, SERP, backlink, and ranking data.
- Google Search Console and analytics services for site performance.
- Social channel APIs for scheduled publishing.
Key Storage
API keys and tokens should be stored through the app settings. Publishing tokens are stored in the operating system keychain where supported. Avoid pasting secrets into campaign prompts or content fields.
MCP Integrations
1MarketingTool exposes its rank, keyword, content, video, and browser tools through a single local onemarketingtool MCP server. Use it when you want compatible AI clients to reach app-specific workflows from your machine — see MCP Integrations.
Troubleshooting
If a provider fails, check the exact error in Logs or the relevant settings screen. Most failures are caused by missing API permissions, expired tokens, or a CLI that is not on the system path.