AI & API

Setup guide · any MCP client

A remote MCP server for your content.

LimeGhost runs a remote MCP server over HTTP with OAuth sign-in. Any client that supports remote servers can connect, work across every project you can open, and use the same tools Claude and ChatGPT use.

Server URL

https://limeghost.com/api/mcp
A notebook and a fountain pen beside a printed agenda
Same tools, any client.

Setup

Connect any client.

  1. 1

    In your client, add a remote MCP server (HTTP transport) with the server URL above.

  2. 2

    Your client opens LimeGhost's sign-in: enter your e-mail code and click Allow. Sign-in is OAuth 2.1 with PKCE; dynamic client registration and client ID metadata documents are both supported.

  3. 3

    Start with list_projects, then get_project_context for the project you want. Every project tool takes a project_id.

Responses are plain JSON over HTTP — no streaming subscriptions. Each person can make up to 120 tool calls a minute.

Then ask

Talk to it like a colleague who knows the project.

Start with “list my projects” — every request names the project it's for, so one assistant can work across all your brands.

  • “Save this as an idea for my Grow Commercial project.”

    Lands in the idea hub, ready to become a post.

  • “Plan next week: two LinkedIn posts and a Bluesky thread from my newest ideas.”

    Drafts on the calendar, waiting for your review.

  • “Which of last month's posts beat my usual, and why?”

    An answer from your own analytics, not an industry average.

What a connected assistant can do.

  • Projects

    Find your projects and read one's context: what it's about, its brand kit, channels, ideas and upcoming calendar.

    • list_projects
    • get_project_context
  • Ideas

    Read the idea hub, save new ideas, update them and read their attachments.

    • list_ideas
    • read_ideas
    • read_attachments
    • create_ideas
    • update_ideas
  • Posts

    Draft posts in your voice, revise them, review them against each network's rules, and edit them.

    • list_posts
    • read_posts
    • review_posts
    • write_posts
    • revise_posts
    • create_draft_posts
    • update_posts
    • get_job_results
  • Planning & publishing

    Put posts on the calendar, schedule them, publish now or take a post down — always on your explicit ask.

    • plan_posts
    • publish_posts
    • unpublish_posts
  • Images

    Generate images in your brand kit, browse the media library and attach pictures to posts.

    • list_media
    • generate_images
    • retry_media_generation
    • update_media
    • attach_media
  • Brand kits

    List and read the project's brand kits, so images and copy stay on-brand.

    • list_brand_kits
    • read_brand_kits
  • Analytics

    Ask how posts and channels performed, against your own usual.

    • query_analytics

The rules

It acts as you. Only where you allow it.

01

As you, nobody else

Sign-in is your normal e-mail code. The assistant sees what you can see and nothing more.

02

You confirm the big things

Publishing and unpublishing are flagged so your assistant asks before it acts.

03

An owner's switch

Workspace owners can turn AI tools off for the whole workspace, instantly.

04

Revoke in one click

Settings → MCP lists every assistant you connected. Revoking one cuts it off immediately.

05

Same credits as the app

Drafts, images and companion turns use your AI credits, whoever asked for them.

06

No deletes, no settings

Assistants can't delete your ideas, posts or projects, change settings or research the web for you. Those stay in the app.


FAQ

Questions, answered.

Not for MCP — it signs in as you with OAuth, so access follows your memberships. For key-based automation, use the REST API with a workspace API key.

A Georgian townhouse office in Bath with a navy door, in the morning

Next Monday, 8:40

Let your assistant fill the calendar. You stay the editor.

No credit card · 100 AI credits included