Use Praeko with Amp
Connect the agent to the Praeko MCP server, put the API rules in the project's rules file and ask for a schedule in plain language.
Not verifiedPraeko MCP: liveChecked in the vendor's docs on Nov 7, 2026
The Praeko MCP server accepts two credentials: an API key in the Authorization: Bearer header, or OAuth sign-in. With sign-in, the agent opens the Praeko screen in your browser; you choose Read or Write (API keys, channels, members and settings are never granted) and the workspace, then click Allow. The connection is listed under Agent connections, on the API keys page of the panel, where you can revoke it. The sign-in token only works on MCP: the REST API, and the curl that uploads a local file, use the key.
What you get
| Piece | Does | Key scope |
|---|---|---|
| MCP server | 18 tools: searches and reads the docs; reads channels, media, posts, calendar, metrics and usage; uploads media from a URL or, with a shell, from a local file (create_media_upload); and creates, schedules, edits and cancels posts, always in two steps (preview and code). Tools | read to read, write to act |
| Rules file | Teaches the agent the API rules (in Amp: Not verified). | Uses no key |
| Starter prompt | A ready-made first request that checks the connection. | read |
MCP server setup
To be confirmedThe exact format to register a remote MCP server with an Authorization header in Amp has not been checked for this page yet. Use the path that does not depend on it: the plain-text docs (below) and the API directly.
Without MCP: what any agent can use
| Path | Where |
|---|---|
| Plain-text docs index | /llms.txt and /llms-full.txt |
| Every page in Markdown | Add .md to the URL, or use Copy as Markdown |
| Full contract | /openapi.json |
| API directly | Get started in 5 minutes |
Question or mistake on this page? contato@praeko.appView .md