Claude wants to post on LinkedIn and X
Founder series #4, Tue, Nov 10 at 9:00
Connect the AI you already use, like Claude or ChatGPT. It writes and schedules your posts, tells you which ones brought in customers, and keeps your CRM up to date. By default, nothing goes out until a person says yes.
Claude wants to post on LinkedIn and X
Founder series #4, Tue, Nov 10 at 9:00
Works with
It takes a few clicks. You sign in to Tracee once, and your AI only sees what your account can see.
Open Claude and go to Settings, then Connectors.
Click Add custom connector and paste your Tracee link.
Click Connect, then sign in to Tracee.
Then try asking
Which of my posts brought in the most leads last month?
Anything your AI wants to post waits in Tracee for a yes first. You can change that in Settings.
Working in a terminal? Use the Tracee CLI, no chat app needed.Set up the CLI
Here's a real request and what your AI does with it. The post at the end is waiting for you.
Tell your AI what you want, in your own words.
It checks your numbers and brand rules, writes a version for each channel and picks a time.
The post waits in Tracee until you say yes, then goes out when it asked to.
Requests from your AI land here.
Nothing is published until a person approves it.
Your AI is quick. Tracee keeps it on your brand, inside your rules and on the record.
Your tone and the words you never use are written down once. Your AI reads them before it writes, and a post that breaks one can't go out until it's fixed.
Posts wait for a person unless you turn that off. Deleting a post, taking one down or changing your CRM always waits. Your AI can't approve anything.
Tracee logs every action, by people and by AI, from the app, MCP, the API or the CLI, with what changed and who did it.
Your AI can see what you spend. It can't change a campaign, a budget or a bid.
ClaudeMCPdraft_post
NoneDraft, 2 channels
ClaudeMCPschedule_post
DraftWaiting for approval
One hosted MCP server with 16 tools, a REST API, and the Tracee CLI. Every call goes through the same policy and audit log as the app.
Tracee MCP server
https://traceeai.com/mcp
https://traceeai.com/mcpTracee CLI
Run Tracee from a terminal: posts, media, brand, the social inbox, Radar, CRM, workflows and analytics. Use it yourself, in scripts, or let Claude Code, Codex or Cursor drive it.
--jsonnpm install -g https://traceeai.com/cli/tracee-cli.tgztracee login # paste your workspace keytracee whoamitracee posts create --body "Dark mode is live" --channel linkedin --publish nowtracee brand learn --url https://acme.comtracee inbox list --view needs_replytracee radar signals --min-strength 3tracee workflows list --json| Agent | How it connects | Sign-in |
|---|---|---|
| ClaudeAnthropic | Custom connector with the MCP link | OAuth sign-in |
| Claude CodeAnthropic | claude mcp add --transport http | OAuth sign-in |
| ChatGPTOpenAI | Connector in developer mode | OAuth sign-in |
| CursorAnysphere | Entry in mcp.json | OAuth sign-in |
| Gemini CLIGoogle | gemini mcp add --transport http | OAuth sign-in |
| OpenAI APIResponses API, Agents SDK | MCP tool with a bearer token | Workspace key |
| Any MCP clientOpen standard | Streamable HTTP | OAuth or workspace key |
| Tracee CLIYour terminal, scripts, coding agents | tracee login | Workspace key |
| REST APIYour own code | HTTPS and JSON at /api/v1 | Workspace key |
| Tool | What it's for | Actions |
|---|---|---|
| workspaces | Which workspace this connection acts on, for people in more than one. |
|
| channels | Where posts can go, each network's rules and live options, and links to connect more. |
|
| brand | Your brand profile and assets, learned from your site. Agents read it before they write; only people change tone and banned phrases. |
|
| memory | What the team asked to be remembered: preferences, goals, what worked, and live numbers. |
|
| web | Read any page, find its pictures, search the web. |
|
| media | AI images and videos on brand, the library, files from Drive or Dropbox, and clips cut from long videos. |
|
| posts | Draft, schedule, publish and take down posts, with one version per channel. |
|
| approvals | What is waiting for a person, and what they decided. Agents can't approve. |
|
| inbox | Comments, DMs and mentions from every channel: replies drafted in your voice. |
|
| analytics | The contacts, MQLs and revenue each post and campaign brought in, engagement, website traffic and tracking health. |
|
| radar | Social listening: what people say about you and competitors, and buying signals. |
|
| crm | Contacts from eight CRMs and leads from forms and bookings, each one's first touch, and the funnel by source. |
|
| ads | Spend, clicks and cost per lead on every connected ad platform. Read only: no tool changes a budget. |
|
| research | Live lookups: companies, people, keyword demand, trends and the ads competitors run. |
|
| apps | Any action in an app you connected, like HubSpot, Slack, Gmail, Notion or Google Sheets. Reads run; changes wait. |
|
| workflows | Automations built as drafts that a person reviews and turns on. |
|
Sign-in, approvals, the audit log and what your AI can't touch.
Start a free trial, connect your AI with one link, and approve its first post.