New: your gimmefy account now travels into Claude, ChatGPT, Codex, Copilot, Gemini workflows and any MCP-ready client

gimmefy MCP connector

Use gimmefy from the frontier workspace you love.

Claude for writing. ChatGPT for thinking. Gemini for exploration. gimmefy for the work underneath.

Connect your gimmefy account once with MCP, then use your brand vaults, projects, skills, playbooks, focus groups, visuals and model choices from the AI platform you already want to work in.

Set it up in five minutes See where it works

Connector URL

https://mcp.gimmefylabs.com/mcp

Mix and match the frontier

The fun part is what becomes possible.

You no longer have to leave your favourite AI workspace just because the next step lives somewhere else. MCP turns gimmefy into the layer that travels with you.

1

Make visuals from Claude

Claude is a wonderful thinking partner. Native Claude is not your Visual Hub. With gimmefy connected, it can ask your account to create branded images and send the result back.

2

Bring brand vaults into ChatGPT

Use ChatGPT as the conversation surface, but let gimmefy carry the brand memory: tone, offers, guardrails, projects and the details your team should not have to paste again.

3

Run focus groups from Gemini

Ask from a Gemini workflow and use gimmefy to run Focus Group, Model Council, multi-agent thinking or a full playbook behind the scenes.

4

Let models cross the room

Ask from one frontier client while gimmefy routes the work through the right model or capability underneath. Your chat app is the seat. gimmefy is the model-agnostic engine.

Quick start · about five minutes

Connect once. Then just ask.

No new MCP account. No new workspace to babysit. Use the same gimmefy platform login you already use, then work from wherever your brain is happiest today.

1

Open connector settings

In your AI client, find connector or MCP settings. In Claude, go to Customize → Connectors.

2

Add a custom connector

Choose the custom connector or remote MCP option. Name it whatever your team will recognise.

3

Paste the URL

Use https://mcp.gimmefylabs.com/mcp as the connector address.

4

Sign in normally

Click connect, then sign in with your regular platform email and password.

5

Set your brand

Tell the assistant which brand vault and project to use. After that, brief it in plain English.

Claude setup

If Claude is where you think, bring gimmefy there.

Claude can become a front door to your gimmefy account: brand context, visuals, playbooks, focus groups and the platform work Claude does not run natively.

Connect gimmefy to Claude

  1. Go to Customize → Connectors On Claude web or desktop, open connector settings.
  2. Click Add custom connector On Team or Enterprise plans, an owner may need to add it for the organisation first.
  3. Paste the MCP URL https://mcp.gimmefylabs.com/mcp
  4. Click Connect and sign in Use your normal platform login. The connector inherits your existing permissions.
  5. Set your brand vault Try: “Set my brand to [Brand Vault] and my project to [Project].”

Where it works

MCP makes gimmefy portable.

Different AI clients expose MCP differently. The connector address stays the same; the setup path changes by client. The point is freedom, not another place to log into.

Claude

Custom connector

Use Claude for the thinking and gimmefy for the brand-aware platform work underneath.

Customize → Connectors → Add custom connector

ChatGPT

Brand memory

Let ChatGPT conversations reach your gimmefy brand vaults, projects and approved capabilities.

Apps / custom app setup → MCP-backed tools

Codex

Build threads

Keep implementation work close to the marketing assets, briefs and campaign context it depends on.

codex mcp add gimmefy --url https://mcp.gimmefylabs.com/mcp

GitHub Copilot

MCP surfaces

Bring gimmefy context into supported Copilot surfaces when product and marketing work meet.

Copilot MCP settings → add remote MCP server

Gemini

Multi-agent runs

Use Gemini workflows to kick off gimmefy playbooks, Focus Group, Model Council and model-routed work.

Gemini CLI / API workflow → MCP server configuration

Other MCP clients

Same URL

If your client supports remote MCP with authentication, use the same connector URL.

https://mcp.gimmefylabs.com/mcp

What to ask

Ask for the thing, not the tool.

Start by setting the brand and project. Then ask for the result. gimmefy can pick up the right capability, model, vault or playbook behind the scenes.

Context

“Set my brand to [Brand Vault] and my project to [Project].”

Strategy

“Use our brand vault and write the creative brief for the launch.”

Campaign

“Give me three campaign concepts, generate hero visuals for the strongest one, then turn it into a launch email.”

Playbook

“Run the Campaign Creator playbook, test the idea with Focus Group and send me the result link when it is ready.”

Access and privacy

Your account is the boundary.

The connector does not create a new workspace or a shared back door. It uses your normal gimmefy account, your normal permissions and your normal credits.

Only your stuff

The client can only access the brand vaults, projects and tools your gimmefy account can see.

Same login

Use the email and password you already use for the platform.

Same credits

Runs spend your normal account credits. Check your balance in the platform.

Results come home

Generated assets and run outputs link back to your own platform account.

FAQ

The small print, in human.

What is MCP?

MCP, or Model Context Protocol, is a standard way for AI clients to connect to external tools and context. In this case, it lets an AI client use gimmefy through your account.

Do I need a new gimmefy account?

No. Use your regular gimmefy platform account. If you are on a partner-branded platform, use that same platform login.

Why is the connector called gimmefy in my white-label account?

Some partner connectors may show the gimmefy name while custom branding is being completed. The visible name does not change your permissions, vault access or project access.

Can the AI see other customers?

No. The connector follows your account permissions. It can only use what your account can access inside the platform.

What if the output ignores my brand?

Set your brand vault again: Set my brand to [Brand Vault]. Then ask for the work again with that context active.

What if I cannot add a connector?

Check whether your AI client plan supports custom connectors or remote MCP. For team plans, an admin or owner may need to enable it first.

Ready when you are

Your marketing infrastructure should travel with you.

Claude today. ChatGPT after lunch. Gemini when you want another angle. Same account, same brand context, same work coming back to gimmefy.

Start with the five-minute setup Open platform