Scripe MCP Server
fcastrosantosapliqo/scripe-mcp
Integração nativa Scripe para Claude — gerencie conteúdo via MCP
Ver no GitHubServidor MCP que integra a API Scripe ao Claude Code e clientes MCP compatíveis. Gerencia posts, notas, projetos e jobs assíncronos diretamente pela IA, sem sair do seu fluxo de trabalho.
Instalação
npx convez-ai fcastrosantosapliqo/scripe-mcp1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Gerar posts de conteúdo assistidos por IA a partir de notas e transcrições
- Automatizar fluxos de aprovação e agendamento de posts em projetos
- Gerenciar espaço de trabalho, projetos e fontes de conteúdo via Claude Code
Veredito

Implementação MCP bem estruturada e documentada para usuários Scripe que querem automatizar workflows de conteúdo via Claude. Requer plano Advanced/Business na Scripe e conhecimento básico de configuração de MCP servers.
README
A tradução para o português deste README ainda está na fila.
scripe-mcp
A Model Context Protocol (MCP) server for the Scripe API. Lets you manage posts, notes, projects, and async jobs directly from Claude Code or any MCP-compatible client.
Requirements
- Node.js 18+
- A Scripe API key (Advanced or Business plan)
Installation
git clone https://github.com/fcastrosantosapliqo/scripe-mcp.git
cd scripe-mcp
npm install
npm run build
Configuration
Claude Code
Add the following to your ~/.claude/claude.json under mcpServers:
{
"mcpServers": {
"scripe": {
"command": "node",
"args": ["/absolute/path/to/scripe-mcp/dist/index.js"],
"env": {
"SCRIPE_API_KEY": "scripe_sk_live_..."
}
}
}
}
Other MCP clients
Run the server directly, passing your API key as an environment variable:
SCRIPE_API_KEY=scripe_sk_live_... node dist/index.js
The server communicates over stdio, which is the standard transport for MCP.
Available tools
Workspace & projects
| Tool | Description |
|---|---|
scripe_get_workspace | Current workspace and principal info |
scripe_list_projects | Paginated list of all projects |
scripe_get_project | Single project by ID |
Posts
| Tool | Description |
|---|---|
scripe_list_posts | List posts for a project; filter by status and/or date range |
scripe_get_post | Single post by ID |
scripe_create_post | Create a draft or scheduled post |
scripe_generate_post | AI-generate a post from raw text or a note (async — returns a job) |
Post statuses: waitingProcessing · draft · waitingApproval · approved · rejected · scheduled · published · suggested
Notes
| Tool | Description |
|---|---|
scripe_list_notes | List notes for a project; filter by folder and/or date range |
scripe_get_note | Single note by ID |
scripe_create_note | Create a note (also queues a content slot) |
Sources
| Tool | Description |
|---|---|
scripe_get_source | Read a source/transcription (truncated to 2,000 chars) |
scripe_create_source | Push a text transcript into Scripe as a source |
Async jobs
| Tool | Description |
|---|---|
scripe_list_jobs | Paginated list of async jobs |
scripe_get_job | Single job with current status and progress |
scripe_cancel_job | Cancel a queued job |
Health
| Tool | Description |
|---|---|
scripe_health | Unauthenticated liveness probe |
Typical workflows
Draft a post from scratch
1. scripe_list_projects → pick a projectId
2. scripe_create_post → projectId + content + title
AI-generate a post from notes
1. scripe_list_notes → find the noteId
2. scripe_generate_post → noteId + projectId → returns jobId
3. scripe_get_job (poll) → wait for status DONE
4. scripe_list_posts → retrieve the generated draft
Push a transcript and generate a post
1. scripe_create_source → content (transcript text)
2. scripe_generate_post → text (transcript) + projectId → jobId
3. scripe_get_job (poll) → wait for status DONE
Development
npm run dev # run from source with tsx (no build step)
npm run build # compile to dist/
npm start # run compiled output
API reference
Full Scripe API documentation: apidocs.scripe.io
License
ISC