Skip to content
MagicHub
Start free

MagicHub MCP

Bring company context into the work you already do.

When enabled for your workspace, the MagicHub MCP lets supported AI clients work with the company and customer context you are allowed to see. Use it in Codex or Claude for setup, CRM research, outreach preparation and blog drafts, while MagicHub keeps the shared records and permissions.

MCP access requires a separately authorized client connection and a workspace where the relevant capability is enabled.

The customer story 01
AS
Acme ServicesA relationship, with context.
ConversationCommitmentNext step
Everything connects.
The financial picture 02
A$15,000Planned quarterly revenue
One commitment. A clearer plan.
Connected-workspace concept · sample data

One shared workspace

Updates and reviewed work live in MagicHub, so authorized clients can work from the same company context.

Your access still applies

Your MagicHub account and company permissions determine what the assistant can read or change.

Review before action

Drafts stay drafts until you review them; consequential actions require an explicit approval step.

01 / What it can help with

Workflows and connection status

The client can help prepare and organize work. Each workflow still follows the access and approval rules of the selected MagicHub company.

Company setup

Read setup state; Save answers and review changes; Apply approved setup.

CRM

Read company records; Read contact context; Read daily leads.

Outreach

Read outreach pipeline; Prepare outreach drafts; Queue or update approved outreach delivery.

Company blog

Read blog settings and articles; Save blog drafts; Schedule or cancel an article.

Connection status

Prepare connection approval; Read connection diagnostics.

02 / Shared progress

The work stays with the company

Company setup answers and applied settings are stored in MagicHub. Outreach and blog work is saved against the selected company, so an authorized person can review the same progress in MagicHub and in another connected client.

Conversation history and sign-in sessions remain separate inside Codex and Claude. Connecting both clients does not copy a token, session or browser profile from one to the other.

A company selector is not permission

Selecting a company tells the connection which workspace to use. MagicHub still checks your account's company access and action permissions for each request.

03 / Access and review

Authentication, company access and approval each have a job

04 / Getting started

Connect Codex or Claude

The connection is configured in each AI client. Access depends on an enabled MagicHub workspace and a completed authorization flow.

Codex

Add MagicHub as a remote MCP connection, then complete the client sign-in prompt.

  • Use the MagicHub MCP connection details provided for your workspace
  • Complete authorization in Codex when prompted
  • Choose the company you are allowed to access
  • Ask a company manager to approve the pending connection in AI assistants settings

Claude

Add MagicHub as a remote MCP connection, then authorize it in Claude.

  • Use the same workspace connection details in Claude
  • Complete authorization in Claude's MCP connection flow
  • Choose the company you are allowed to access
  • Approve Claude's separate pending connection in AI assistants settings

Before you begin

The workspace owner can confirm that MCP access and the workflows you need are enabled.

  • You need a MagicHub account with permission for the selected company
  • Each AI client needs its own authorization
  • Existing OAuth connections to other services remain separate

MagicHub MCP questions

Keep the company record at the centre

Use an AI client to prepare the work, then keep the shared company context and review steps in MagicHub.

See how Magic connectsRead about security