Techtenstein Seo vs Apple Ads MCP
A side-by-side look at the Techtenstein Seo and Apple Ads MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Techtenstein Seo for marketing work as a local process; choose Apple Ads MCP for marketing as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Techtenstein Seo when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
TECHTENSTEIN_API_KEY.
Choose Apple Ads MCP when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
APPLE_ADS_ALLOW_DELETES.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 36/100 · Fair | 45/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | TECHTENSTEIN_API_KEY | APPLE_ADS_ALLOW_DELETES |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 6 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Techtenstein Seo | View Apple Ads MCP |
Tools & capabilities
Techtenstein Seo tools
No tool names declared yet. Check the project README from the listing page.
Apple Ads MCP 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.
Techtenstein Seo
{
"mcpServers": {
"techtenstein-seo": {
"command": "uvx",
"args": [
"techtenstein-seo-mcp"
],
"env": {
"TECHTENSTEIN_API_KEY": "YOUR_TECHTENSTEIN_API_KEY_HERE"
}
}
}
}
Apple Ads MCP
{
"mcpServers": {
"apple-ads-mcp": {
"command": "npx",
"args": [
"--yes",
"markdownlint-cli2@0.23.2"
],
"env": {
"APPLE_ADS_ALLOW_DELETES": "YOUR_APPLE_ADS_ALLOW_DELETES_HERE"
}
}
}
}
Frequently asked questions
Techtenstein Seo is categorized under Marketing and uses a local stdio subprocess. Apple Ads MCP belongs to Marketing and uses a local stdio subprocess. Pick Techtenstein Seo for marketing work and Apple Ads MCP 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.
Techtenstein Seo has no declared pricing — check the project's own site. Apple Ads MCP 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 techtenstein-seo and apple-ads-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Techtenstein Seo has a quality signal of 36/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Apple Ads MCP has 45/100 (Fair) with 1 views, 0 installs and 6 GitHub stars.