mcp-server
CLAUDE.md21 starsChanged 25 days agoMITView on GitHub
This is the @synterai/mcp-server — the public-facing MCP SDK that wraps the synter-media backend. This is a published npm package (@synterai/mcp-server). Everything here is public. No internal credentials, account IDs, or proprietary logic. BEFORE any action that touches an external system, verify you are in the mcp-server project. This MCP server is a public-facing SDK used by external developers. Any breaking change, bad publish, or accidental credentials exposure affects all users of the package. This is the Model Context Protocol…
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- llms.txtllms.txt
- budget-optimizerSkill
- campaign-managerSkill
- competitor-researchSkill
- creative-generatorSkill
- performance-analyzerSkill
- synter-adsSkill
The file
We split this CLAUDE.md into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 34
Never hardcode API keys, tokens, or secrets in source files.
- Very specific: line 35
Always bump the version in package.json before publishing.
- Very specific: line 36
Test locally with node dist/index.js before publishing to npm.
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Claude Code Instructions — @synterai/mcp-server
Project Ecosystem
This is the @synterai/mcp-server — the public-facing MCP SDK that wraps the synter-media backend.
| Project | Relationship | Rules of engagement |
synter-media | This SDK wraps synter-media's API. Changes to synter-media's API surface may require updates here. | Always check synter-media's route definitions before adding/changing tools. Never expose internal synter-media endpoints that aren't intended to be public. Version-bump before publishing. |
synter-docs | Docs for this SDK live in synter-docs. | When tools change here, flag synter-docs needs updating. |
jobs-outreach-engine | No direct dependency. | — |
gumshoe | Completely separate. | Never reference Gumshoe in this package. |
This is a published npm package (@synterai/mcp-server). Everything here is public. No internal credentials, account IDs, or proprietary logic.
CRITICAL: Workspace & Account Verification
BEFORE any action that touches an external system, verify you are in the mcp-server project.
| Check | Expected value | Action if wrong |
| Working directory | /Users/joelhorwitz/work/mcp-server/ | STOP — ask user to confirm |
| Package name | @synterai/mcp-server (check package.json) | STOP if different |
| GitHub repo | mcp-server repo — NOT jshorwitz/synter-media | STOP before any push |
| npm/registry | Publishing to @synterai scope only | Confirm before npm publish |
| Deployment target | syntermedia.ai MCP endpoint — NOT production Synter app | Confirm before deploy |
This MCP server is a public-facing SDK used by external developers. Any breaking change, bad publish, or accidental credentials exposure affects all users of the package.
Additional safety rules
- Never hardcode API keys, tokens, or secrets in source files.
- Always bump the version in
package.jsonbefore publishing. - Test locally with
node dist/index.jsbefore publishing to npm. - The
skills/andagents/directories contain Synter-specific configs — do not expose internal Synter account IDs or API endpoints in published code.
Project Overview
This is the Model Context Protocol server for Synter's ad management platform. It exposes tools for managing campaigns across Google, Meta, LinkedIn, Microsoft, Reddit, TikTok, and more.
- Entry point:
src/index.ts - Built with TypeScript, compiled to
dist/ - Published as
@synterai/mcp-serveron npm
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.