How to connect Grok Bot to Tracee with a custom MCP connector

Grok Bot 1.0 can read X, join meetings and work in Slack, but its documented X access is read-only and it has no built-in publishing tool for LinkedIn, Instagram or TikTok. This guide adds one: Tracee's remote MCP server, connected as a custom connector.

To connect Grok Bot to Tracee, open Connect apps in the Grok Bot desktop app, choose Add a custom connector, enter the name Tracee, pick Remote HTTPS and use https://traceeai.com/mcp as the server URL. Then sign in to Tracee, or add a workspace key as an HTTP header. It takes about five minutes.

Tracee has no partnership with SpaceXSI (the company formerly called xAI). Every menu name below comes from the Grok Bot docs (last updated November 11, 2026) and Tracee's MCP docs.

What do you need before you start?

You need Grok Bot access, a Tracee workspace with at least one connected channel, and the desktop app. The custom connector form is documented for the desktop app, not the phone.

How do you add Tracee as a custom connector?

Use the custom connector form in Connect apps. Grok Bot's docs describe it this way: "choose Add a custom connector at the bottom of Connect apps. Enter a Name, then pick a Type: Remote HTTPS takes a Server URL, with optional HTTP headers and an OAuth Client ID."

Option A: sign in with your Tracee account (try this first)

Tracee's MCP server signs people in with OAuth 2.1, with dynamic client registration and PKCE, so it doesn't need a client ID from you.

1. Open the Grok Bot desktop app and choose Connect apps in the sidebar.
2. Scroll to the bottom and choose Add a custom connector.
3. Name: Tracee.
4. Type: Remote HTTPS.
5. Server URL: https://traceeai.com/mcp.
6. Leave HTTP headers and OAuth Client ID empty.
7. Choose Add plugin to save it.
8. If the connector shows Needs auth, choose Authenticate and sign in to Tracee in the browser window that opens. Pick the workspace and allow access.
9. Confirm Tracee appears under Installed.

A caveat: Grok Bot's docs don't say whether a custom connector without a client ID completes sign-in through dynamic client registration. If step 8 doesn't open a Tracee sign-in page, use Option B.

Option B: use a Tracee workspace key

Tracee's docs say clients that can't sign in "send a personal or workspace key as Authorization: Bearer <key>".

1. In Tracee, open Settings > Workspace keys and create a key named Grok Bot.
2. In Grok Bot, open Connect apps > Add a custom connector.
3. Name Tracee, type Remote HTTPS, server URL https://traceeai.com/mcp.
4. Under HTTP headers, add the header name Authorization with the value Bearer followed by your key.
5. Choose Add plugin.

A workspace key acts only in that workspace and keeps working if the person who made it leaves (authentication docs). Treat it like a password: it can publish to your channels within your guardrails. Turn it off in Tracee when you stop using the connector.

Option C: ask a Bot to add it

The docs say "a Bot can also add an MCP server that isn't in the catalog, by URL." You can type "Add the MCP server at https://traceeai.com/mcp and call it Tracee." Never paste a key into ordinary chat. Grok Bot's docs say to enter secrets in the masked secret card when a Bot asks for one.

How do you check that it works?

Start a new message, type @ and pick Tracee to attach it to the task, then ask for something read-only. The docs say an app's tools are ready from your next message.

1. "Using Tracee, list my workspaces and connected channels." You should see each channel and whether agents may post to it.
2. "Using Tracee, show my brand rules and banned phrases."
3. "Using Tracee, show what's scheduled for the next 7 days."

If all three answer, the connection works. If the Bot says the app is missing, see the troubleshooting table below.

What should you ask first?

Start with prompts that create drafts, so nothing goes out while you learn how the Bot behaves. These use Tracee's MCP tools for posts, brand, approvals and analytics.

• "Read the last 20 posts that mention our product on X. Pick the three most common questions and draft a LinkedIn post answering each one in Tracee, following our brand rules. Save them as drafts."
• "Take the summary from today's campaign kickoff meeting and draft a launch post for LinkedIn, X and Threads in Tracee. Schedule them for Tuesday at 9:00 in my time zone."
• "Turn this blog URL into one post per connected channel in Tracee. Keep X under 280 characters and add the link to every version."
• "Using Tracee analytics, which of last month's posts brought in the most clicks, and what did they have in common?"

Tracee holds each version to its network's rules. A version that uses a banned phrase is flagged and can't go out until it is fixed. For more on writing rules agents follow, see brand voice rules for AI-written posts.

How do approvals work on both sides?

There are two checkpoints, and you should keep both.

In Grok Bot, approvals depend on the tool, the risk and your Auto-review rules. The FAQ recommends "narrow Ask first rules for actions such as sending, publishing, deleting, purchasing". Add one for Tracee's publish and schedule actions under Settings > General > Bot > Custom Rules. Approvals raised by a routine expire after about 30 minutes, and the action then doesn't run (troubleshooting).

In Tracee, agent publishing and scheduling file an approval request by default instead of going out. The setting lives under Settings > Agent rules, next to the list of channels agents may post to (guardrails docs). Deleting a post, taking a live post down and write actions in connected apps always wait for a person, and agents can't approve anything. When the Bot calls the tool, the answer says "Sent for approval", which means it worked. Every agent action lands in Tracee's audit log under the connection's name.

How do you use Tracee from a Team Bot?

A Team Bot uses the apps its owner added. The Team Bots docs say: "In Slack channels, threads, and group chats, a Team Bot uses only its owner's apps, and asks before it uses your accounts."

For a social team, that means:

1. The Team Bot's owner adds the Tracee connector, ideally with a workspace key (Option B), so access belongs to the workspace and survives staff changes.
2. In a Slack thread, anyone the Bot is shared with can ask it to draft or schedule posts. Approval cards in a thread can be answered only by the person who asked.
3. The final approval still happens in Tracee, where your approvers see the post exactly as it will publish.

Grok Bot also offers shared connectors: a Manager can share their own account with everyone who uses the Bot. That needs a team admin to turn on Allow Shared Logins, which is off by default. A workspace key on the owner's connector is simpler to reason about.

What do Enterprise admins need to allow?

Grok Bot inherits the team's Cursor connector policy, managed on the Plugins & MCPs page of the Cursor dashboard (teams and enterprises docs). Check three things:

• Connector policy. A blocked server shows as Disabled by team admin, and the docs say a custom server blocked by policy "can't be saved".
• MCP allowlist (Enterprise only). Add https://traceeai.com/mcp if your team uses an allowlist.
• Network Controls (Enterprise only). In an allowlist mode, Apply to MCP servers (off by default) makes every connected app match an allowed destination. Add traceeai.com to the team allowlist if it is on.

How do you fix common problems?

If re-authorizing completes but the connector still shows disconnected, Grok Bot's docs suggest contacting their support with the app name.

Can you run this on a schedule?

Yes. In Grok Bot, a routine assigns a task to one Bot and tells it when to run. Test the task once by hand, then ask: "Every Monday at 8:00, read last week's top mentions on X, draft three posts in Tracee for the week and send me a summary." The drafts wait in Tracee for approval, so a routine can't publish on its own.

Next step

Connect Tracee with Option A, run the three read-only checks, then try one draft prompt and approve the result in Tracee. If you want the background on what Grok Bot 1.0 can and can't do, read our Grok Bot 1.0 overview for marketers.