Use Amelia in AI assistants

Connect your Amelia Vibe account to an assistant and ask Amelia to find drafts, write a post from your notes, edit it, or schedule it. She uses your saved context and learned topics. These connections never post immediately. A scheduled post publishes automatically at its time, without another review. Confirm the text and time before scheduling.

Server address

https://ameliavibe.com/api/mcp

Choose OAuth when asked for a sign-in method, then sign in to Amelia Vibe and approve access. You don't need an API key. Your assistant can access your own account; it can't browse another person's account.

Claude

Open Customize → Connectors. When Amelia Vibe appears in the directory, select it and connect. Otherwise, choose Add → Add custom connector (or Custom → Web), name it Amelia Vibe, and paste the server address. Choose Sign in now and Register automatically for the OAuth client. Finish signing in, then enable the connector in your chat. An organization administrator may need to add it first. See Claude's setup guide.

Try: “Show my recent drafts” or “Draft a post about this lesson from my week: …”.

ChatGPT

Open Plugins and search for Amelia Vibe. When the listing is available, install it and connect your account. Type @Amelia Vibe in the message box to select it explicitly. Availability of write actions depends on your ChatGPT account and organization settings.

If you cannot find the listing, you can add Amelia Vibe with the server address. For a Business, Enterprise or Edu workspace that permits custom connections, open Plugins → + → Add custom MCP server, paste the server address, choose OAuth, and install the resulting plugin. Ask your administrator if the option is missing. OpenAI's custom-server guide describes the setup.

Grok

Open grok.com/connectors, then New Connector → Custom. Paste the server address, sign in, and ask for your recent drafts. This custom connection does not require a directory listing.

Muse

When Amelia Vibe becomes available in Settings → Connectors, connect your account there. If you cannot find it, add it with the server address. Each tool below is labeled Read, Write or Sensitive write. Scheduling is a sensitive write because the post publishes later without another review.

Microsoft 365 Copilot

This connection is for work accounts. Your administrator must enable it before you can use it. The admin setup starts at Microsoft 365 admin center → Copilot → Connectors → Create a new connector → Connect to MCP server. Once your organization makes Amelia Vibe available, sign in to your account and ask for a draft. Your administrator can add the connection with the server address.

Other assistants

Use the same server address and OAuth sign-in. These are host setup paths; compatibility with your account may vary.

• Perplexity: Account settings → Connectors → Custom connector → Remote, for Pro and above. Setup information.
• Le Chat / Mistral: use Studio → Connectors to register a custom MCP connection; administrators manage access in Admin → Administration → Connectors. Mistral's connector guide.
• Cursor: manage servers under Customize → MCPs. For a custom server, add {"mcpServers":{"amelia-vibe":{"url":"https://ameliavibe.com/api/mcp"}}} to your personal ~/.cursor/mcp.json, then complete sign-in. Cursor's guide.
• Raycast: run Install MCP Server, choose HTTP and enter the address, then Sign In. Raycast's guide.

Tool reference

This section is for people configuring or reviewing a connection. All tools require authorization. Invalid inputs are rejected. Reads share a limit of 60 calls per minute per user; writes share 20. Requests also share 60 per minute per IP address. If a limit is reached, wait before retrying. Account limits still apply to drafting. IDs below are UUIDs.

post_list: Read

Optional inputs: status (draft, scheduled, published), limit (1-50, default 20), updated_after, scheduled_after, scheduled_before (timestamps with timezone), and cursor (up to 512 characters). Returns post IDs, titles, statuses, dates and next_cursor. Errors include an invalid cursor or a failed read.

post_get: Read

Input: post_id. Returns the post's title, text, LinkedIn-ready text, media links, status, dates, failure reason and links to LinkedIn and Amelia Vibe. Errors: post not found or a failed read.

profile_read: Read

No inputs. Reports whether setup is finished in onboarded. Returns learned positioning, themes, main and adjacent topics, and post language; missing values may be null. Internal style observations are not returned. Error: profile could not be read.

draft_create: Write

Before a new user’s first draft, Amelia asks two setup questions: their role and why they want to post. For a new request, send brief (1-4,000 characters) and optional material (up to 50,000). To answer questions, send answers_turn_id and answers instead: 1-3 answers, each 1-4,000 characters. Optional idempotency_key (8-128 characters) prevents duplicate requests. Returns working with turn_id, needs_input with questions, drafted with posts, or replied with text; remaining allowance may also appear. After working, wait about 20 seconds before checking status. Errors include invalid answers, reused keys with different content, a request already running, account limits or a generation failure.

draft_status_get: Read

Input: turn_id. Returns the same outcome as draft_create. Use it when drafting takes longer than the initial wait, up to 45 seconds. Errors: turn not found, failed read or the drafting errors above.

draft_preview: Read

Input: post_id. Returns title, text, status, schedule time and an app link, with a card where supported and a text response elsewhere. Errors: post not found or a failed read.

draft_update: Write

Inputs: post_id, replacement content (1-30,000 characters), optional title (up to 200). Returns the updated post and unchanged when appropriate. Only draft or approved posts can be edited; blank text is rejected. Errors: post not found, wrong status or failed update.

draft_schedule: Sensitive write

Inputs: post_id, scheduled_for (up to 40 characters; local date/time in your account timezone or an explicit timezone offset). Returns the schedule time and deferred / needs_reconnect indicators. Confirm the text and time first. The post must be draft or approved, have at least 10 characters, and be scheduled at least 15 minutes ahead. Connections allow up to 50 standing schedules and 20 new schedules per hour. Without LinkedIn connected, the post waits for a connection. Errors include invalid time, unavailable posting access, unsupported company-page posting, wrong status, concurrent changes or schedule limits.

draft_schedule_cancel: Write

Input: post_id. Returns the post to draft status and confirms cancellation. It does not delete the post. Errors: post not found, not scheduled or cancellation failed.

Remove access

In Amelia Vibe, open Settings → Integrations → Connected apps and select Disconnect for the assistant. You can also disconnect it in the assistant. Disconnecting does not cancel existing schedules: cancel those separately if you don't want them to post. See our privacy policy for how connected assistants receive data.