Vibecode Composio

You are building a lean indie version of Composio.

Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt.

===== README.md =====
# Composio indie build

## Goal

Build the smallest trustworthy replacement for the core Composio workflow for one developer or a tiny team.

## Scope

A local MCP server that exposes hand-written tools for the three or four SaaS APIs you actually touch, authenticated with your own personal tokens.

## Quick start

1. Install the documented dependencies.
2. Copy `.env.example` to `.env`.
3. Run the development command chosen during implementation.
4. Complete the acceptance checks in `BUILD_PLAN.md`.

## Honest limits

This build deliberately does not replace:
- Hundreds of pre-built, pre-tested tool schemas you did not have to read API docs for
- Managed OAuth: app registration, consent screens, refresh tokens, revocation
- Per-end-user credential storage, which is the whole game if your agent serves anyone but you
- Someone else fixing your integration when a provider ships a breaking API change
- Usage observability, retries and rate limit smoothing across providers

If those capabilities are essential, use Composio instead of pretending the gap is solved.

===== AGENTS.md =====
# Agent instructions

- Optimize for a working, understandable weekend build.
- Prefer the fewest moving parts that satisfy the brief.
- Do not invent cryptography, security guarantees, APIs, or compliance claims.
- Keep secrets out of source control and logs.
- Add focused tests for destructive, security-sensitive, and data-loss paths.
- Run the project checks before declaring the build complete.
- Record any deliberate shortcut in the README under "Tradeoffs".

===== BUILD_PLAN.md =====
# Build plan

## Original build brief

Build a local MCP (Model Context Protocol) server in TypeScript that gives an AI agent working tools for my own SaaS accounts, using personal access tokens. No hosted service, no accounts, no telemetry.

Stack, non-negotiable:
- Node 20+, TypeScript, pnpm
- @modelcontextprotocol/sdk over stdio transport
- zod for tool input schemas
- undici fetch for HTTP, no per-provider SDKs

Structure:
- src/index.ts: server bootstrap, registers every tool module
- src/providers/gmail.ts, slack.ts, github.ts, notion.ts
- src/http.ts: one shared request helper with timeout, retry on 429 and 5xx with exponential backoff, and error normalization
- .env.example listing every token var, .env gitignored, fail loudly at startup if a token for an enabled provider is missing

Tools to implement, keep them small and honest:
- gmail_search_messages, gmail_get_message, gmail_send_message
- slack_list_channels, slack_post_message, slack_search_messages
- github_list_issues, github_create_issue, github_comment_issue
- notion_search, notion_get_page, notion_append_block
Each tool: zod-validated input, a one-line description an LLM can act on, and output trimmed to useful fields only, never raw API dumps.

In scope: static token auth, a PROVIDERS env var to enable a subset, structured logging to stderr only (stdout is the MCP channel), a vitest suite that mocks HTTP and covers happy path plus 401 and 429 handling.
Out of scope: OAuth flows, multi-user credential storage, a web UI, a database. Say so in the README.

Deliver a README with setup steps, token scope requirements per provider, and the exact JSON block to paste into a Claude Desktop or Cursor MCP config.

## Required capabilities

- Node 20+
- Personal access tokens for each service you want to wrap
- An MCP-capable client such as Claude Desktop, Cursor or your own agent loop

## Delivery order

1. Scaffold the smallest runnable application and document its commands.
2. Implement the primary data model and core workflow.
3. Add validation, safe failure states, and persistence.
4. Cover the critical path with automated tests.
5. Exercise a clean install from the README and fix every missing step.

## Done when

- A new user can go from clone to first successful workflow using only the README.
- The core workflow works without paid infrastructure unless the brief requires it.
- Tests cover the highest-risk behavior.
- Known limitations are explicit rather than hidden.

===== .env.example =====
# Copy to .env and document every variable when it is introduced.
# Never put real credentials in this file.

APP_ENV=development
# Add only values required by the selected implementation.

You are building a lean indie version of Composio.

Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt.

===== README.md =====
# Composio indie build

## Goal

Build the smallest trustworthy replacement for the core Composio workflow for one developer or a tiny team.

## Scope

A local MCP server that exposes hand-written tools for the three or four SaaS APIs you actually touch, authenticated with your own personal tokens.

## Quick start

1. Install the documented dependencies.
2. Copy `.env.example` to `.env`.
3. Run the development command chosen during implementation.
4. Complete the acceptance checks in `BUILD_PLAN.md`.

## Honest limits

This build deliberately does not replace:
- Hundreds of pre-built, pre-tested tool schemas you did not have to read API docs for
- Managed OAuth: app registration, consent screens, refresh tokens, revocation
- Per-end-user credential storage, which is the whole game if your agent serves anyone but you
- Someone else fixing your integration when a provider ships a breaking API change
- Usage observability, retries and rate limit smoothing across providers

If those capabilities are essential, use Composio instead of pretending the gap is solved.

===== AGENTS.md =====
# Agent instructions

- Optimize for a working, understandable weekend build.
- Prefer the fewest moving parts that satisfy the brief.
- Do not invent cryptography, security guarantees, APIs, or compliance claims.
- Keep secrets out of source control and logs.
- Add focused tests for destructive, security-sensitive, and data-loss paths.
- Run the project checks before declaring the build complete.
- Record any deliberate shortcut in the README under "Tradeoffs".

===== BUILD_PLAN.md =====
# Build plan

## Original build brief

Build a local MCP (Model Context Protocol) server in TypeScript that gives an AI agent working tools for my own SaaS accounts, using personal access tokens. No hosted service, no accounts, no telemetry.

Stack, non-negotiable:
- Node 20+, TypeScript, pnpm
- @modelcontextprotocol/sdk over stdio transport
- zod for tool input schemas
- undici fetch for HTTP, no per-provider SDKs

Structure:
- src/index.ts: server bootstrap, registers every tool module
- src/providers/gmail.ts, slack.ts, github.ts, notion.ts
- src/http.ts: one shared request helper with timeout, retry on 429 and 5xx with exponential backoff, and error normalization
- .env.example listing every token var, .env gitignored, fail loudly at startup if a token for an enabled provider is missing

Tools to implement, keep them small and honest:
- gmail_search_messages, gmail_get_message, gmail_send_message
- slack_list_channels, slack_post_message, slack_search_messages
- github_list_issues, github_create_issue, github_comment_issue
- notion_search, notion_get_page, notion_append_block
Each tool: zod-validated input, a one-line description an LLM can act on, and output trimmed to useful fields only, never raw API dumps.

In scope: static token auth, a PROVIDERS env var to enable a subset, structured logging to stderr only (stdout is the MCP channel), a vitest suite that mocks HTTP and covers happy path plus 401 and 429 handling.
Out of scope: OAuth flows, multi-user credential storage, a web UI, a database. Say so in the README.

Deliver a README with setup steps, token scope requirements per provider, and the exact JSON block to paste into a Claude Desktop or Cursor MCP config.

## Required capabilities

- Node 20+
- Personal access tokens for each service you want to wrap
- An MCP-capable client such as Claude Desktop, Cursor or your own agent loop

## Delivery order

1. Scaffold the smallest runnable application and document its commands.
2. Implement the primary data model and core workflow.
3. Add validation, safe failure states, and persistence.
4. Cover the critical path with automated tests.
5. Exercise a clean install from the README and fix every missing step.

## Done when

- A new user can go from clone to first successful workflow using only the README.
- The core workflow works without paid infrastructure unless the brief requires it.
- Tests cover the highest-risk behavior.
- Known limitations are explicit rather than hidden.

===== .env.example =====
# Copy to .env and document every variable when it is introduced.
# Never put real credentials in this file.

APP_ENV=development
# Add only values required by the selected implementation.

You are building a production product version of Composio.

Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt.

===== PRODUCT.md =====
# Composio product brief

## Problem

If you personally use four apps, not four hundred, most of Composio evaporates. An agent can write you a local MCP server that wraps Gmail, Slack, GitHub and Notion with your own personal access tokens in about a session, and the tool-calling loop works fine. What you are actually buying from Composio is the part nobody enjoys: OAuth app registration per provider, token refresh, per-user credential storage, rate limit handling, and schemas for tools you have not thought of yet. That gets ugly the moment you want more than a handful of integrations, or multiple users, or an OAuth flow instead of a static token you pasted in. Solo and token-based: build it. Multi-tenant or breadth-hungry: pay.

## Product outcome

A local MCP server that exposes hand-written tools for the three or four SaaS APIs you actually touch, authenticated with your own personal tokens.

## Target user

A serious builder who needs a maintainable product foundation rather than a one-off demo.

## Required capabilities

- Node 20+
- Personal access tokens for each service you want to wrap
- An MCP-capable client such as Claude Desktop, Cursor or your own agent loop

## Explicit non-goals for v1

- Hundreds of pre-built, pre-tested tool schemas you did not have to read API docs for
- Managed OAuth: app registration, consent screens, refresh tokens, revocation
- Per-end-user credential storage, which is the whole game if your agent serves anyone but you
- Someone else fixing your integration when a provider ships a breaking API change
- Usage observability, retries and rate limit smoothing across providers

## Success criteria

- The primary workflow is measurable end to end.
- Setup is reproducible in a clean environment.
- Failure, recovery, and support paths are documented.
- Product claims match what the implementation actually guarantees.

===== ARCHITECTURE.md =====
# Architecture

## Starting brief

Build a local MCP (Model Context Protocol) server in TypeScript that gives an AI agent working tools for my own SaaS accounts, using personal access tokens. No hosted service, no accounts, no telemetry.

Stack, non-negotiable:
- Node 20+, TypeScript, pnpm
- @modelcontextprotocol/sdk over stdio transport
- zod for tool input schemas
- undici fetch for HTTP, no per-provider SDKs

Structure:
- src/index.ts: server bootstrap, registers every tool module
- src/providers/gmail.ts, slack.ts, github.ts, notion.ts
- src/http.ts: one shared request helper with timeout, retry on 429 and 5xx with exponential backoff, and error normalization
- .env.example listing every token var, .env gitignored, fail loudly at startup if a token for an enabled provider is missing

Tools to implement, keep them small and honest:
- gmail_search_messages, gmail_get_message, gmail_send_message
- slack_list_channels, slack_post_message, slack_search_messages
- github_list_issues, github_create_issue, github_comment_issue
- notion_search, notion_get_page, notion_append_block
Each tool: zod-validated input, a one-line description an LLM can act on, and output trimmed to useful fields only, never raw API dumps.

In scope: static token auth, a PROVIDERS env var to enable a subset, structured logging to stderr only (stdout is the MCP channel), a vitest suite that mocks HTTP and covers happy path plus 401 and 429 handling.
Out of scope: OAuth flows, multi-user credential storage, a web UI, a database. Say so in the README.

Deliver a README with setup steps, token scope requirements per provider, and the exact JSON block to paste into a Claude Desktop or Cursor MCP config.

## Boundaries

Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors.

## Production baseline

- Configuration: validated at startup with safe local defaults where possible.
- Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives.
- Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions.
- Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts.
- Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists.
- Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test.

## Decision records

For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it.

===== AGENTS.md =====
# Agent instructions

- Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code.
- Implement milestone by milestone; keep each change reviewable and leave the application runnable.
- Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present.
- Never invent cryptography or silently weaken a requirement to make a test pass.
- Use provider interfaces for external services and deterministic fakes in tests.
- Add migrations and rollback or recovery notes for persistent data changes.
- Log useful operational context without credentials, tokens, passwords, or personal data.
- Update documentation and run all checks before completing a milestone.

===== MILESTONES.md =====
# Delivery milestones

## M0 — Decisions and scaffold

- Confirm the runtime, persistence model, threat boundaries, and deployment target.
- Create a reproducible local environment and continuous checks.

## M1 — Core workflow

- Implement the smallest end-to-end product path with validation and tests.
- Keep integrations behind interfaces.

## M2 — Trust layer

- Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards.
- Test abuse cases and destructive operations.

## M3 — Operability

- Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration.

## M4 — Release gate

- Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise.
- Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations.

===== OPERATIONS.md =====
# Operations

## Before release

- Validate configuration and secrets at startup.
- Define backup, restore, and rollback procedures and test them.
- Document logs, error tracking, health signals, and alert ownership.
- Set dependency update and vulnerability review expectations.

## Incident checklist

1. Contain the issue without destroying evidence or user data.
2. Record the timeline and affected scope.
3. Rotate exposed secrets and revoke compromised sessions or credentials.
4. Restore from a verified source when needed.
5. Document the root cause, remediation, and regression test.

## Launch constraint

Do not market omitted Composio capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.

# Composio indie build

## Goal

Build the smallest trustworthy replacement for the core Composio workflow for one developer or a tiny team.

## Scope

A local MCP server that exposes hand-written tools for the three or four SaaS APIs you actually touch, authenticated with your own personal tokens.

## Quick start

1. Install the documented dependencies.
2. Copy `.env.example` to `.env`.
3. Run the development command chosen during implementation.
4. Complete the acceptance checks in `BUILD_PLAN.md`.

## Honest limits

This build deliberately does not replace:
- Hundreds of pre-built, pre-tested tool schemas you did not have to read API docs for
- Managed OAuth: app registration, consent screens, refresh tokens, revocation
- Per-end-user credential storage, which is the whole game if your agent serves anyone but you
- Someone else fixing your integration when a provider ships a breaking API change
- Usage observability, retries and rate limit smoothing across providers

If those capabilities are essential, use Composio instead of pretending the gap is solved.

# Agent instructions

- Optimize for a working, understandable weekend build.
- Prefer the fewest moving parts that satisfy the brief.
- Do not invent cryptography, security guarantees, APIs, or compliance claims.
- Keep secrets out of source control and logs.
- Add focused tests for destructive, security-sensitive, and data-loss paths.
- Run the project checks before declaring the build complete.
- Record any deliberate shortcut in the README under "Tradeoffs".

# Build plan

## Original build brief

Build a local MCP (Model Context Protocol) server in TypeScript that gives an AI agent working tools for my own SaaS accounts, using personal access tokens. No hosted service, no accounts, no telemetry.

Stack, non-negotiable:
- Node 20+, TypeScript, pnpm
- @modelcontextprotocol/sdk over stdio transport
- zod for tool input schemas
- undici fetch for HTTP, no per-provider SDKs

Structure:
- src/index.ts: server bootstrap, registers every tool module
- src/providers/gmail.ts, slack.ts, github.ts, notion.ts
- src/http.ts: one shared request helper with timeout, retry on 429 and 5xx with exponential backoff, and error normalization
- .env.example listing every token var, .env gitignored, fail loudly at startup if a token for an enabled provider is missing

Tools to implement, keep them small and honest:
- gmail_search_messages, gmail_get_message, gmail_send_message
- slack_list_channels, slack_post_message, slack_search_messages
- github_list_issues, github_create_issue, github_comment_issue
- notion_search, notion_get_page, notion_append_block
Each tool: zod-validated input, a one-line description an LLM can act on, and output trimmed to useful fields only, never raw API dumps.

In scope: static token auth, a PROVIDERS env var to enable a subset, structured logging to stderr only (stdout is the MCP channel), a vitest suite that mocks HTTP and covers happy path plus 401 and 429 handling.
Out of scope: OAuth flows, multi-user credential storage, a web UI, a database. Say so in the README.

Deliver a README with setup steps, token scope requirements per provider, and the exact JSON block to paste into a Claude Desktop or Cursor MCP config.

## Required capabilities

- Node 20+
- Personal access tokens for each service you want to wrap
- An MCP-capable client such as Claude Desktop, Cursor or your own agent loop

## Delivery order

1. Scaffold the smallest runnable application and document its commands.
2. Implement the primary data model and core workflow.
3. Add validation, safe failure states, and persistence.
4. Cover the critical path with automated tests.
5. Exercise a clean install from the README and fix every missing step.

## Done when

- A new user can go from clone to first successful workflow using only the README.
- The core workflow works without paid infrastructure unless the brief requires it.
- Tests cover the highest-risk behavior.
- Known limitations are explicit rather than hidden.

# Copy to .env and document every variable when it is introduced.
# Never put real credentials in this file.

APP_ENV=development
# Add only values required by the selected implementation.

# Composio product brief

## Problem

If you personally use four apps, not four hundred, most of Composio evaporates. An agent can write you a local MCP server that wraps Gmail, Slack, GitHub and Notion with your own personal access tokens in about a session, and the tool-calling loop works fine. What you are actually buying from Composio is the part nobody enjoys: OAuth app registration per provider, token refresh, per-user credential storage, rate limit handling, and schemas for tools you have not thought of yet. That gets ugly the moment you want more than a handful of integrations, or multiple users, or an OAuth flow instead of a static token you pasted in. Solo and token-based: build it. Multi-tenant or breadth-hungry: pay.

## Product outcome

A local MCP server that exposes hand-written tools for the three or four SaaS APIs you actually touch, authenticated with your own personal tokens.

## Target user

A serious builder who needs a maintainable product foundation rather than a one-off demo.

## Required capabilities

- Node 20+
- Personal access tokens for each service you want to wrap
- An MCP-capable client such as Claude Desktop, Cursor or your own agent loop

## Explicit non-goals for v1

- Hundreds of pre-built, pre-tested tool schemas you did not have to read API docs for
- Managed OAuth: app registration, consent screens, refresh tokens, revocation
- Per-end-user credential storage, which is the whole game if your agent serves anyone but you
- Someone else fixing your integration when a provider ships a breaking API change
- Usage observability, retries and rate limit smoothing across providers

## Success criteria

- The primary workflow is measurable end to end.
- Setup is reproducible in a clean environment.
- Failure, recovery, and support paths are documented.
- Product claims match what the implementation actually guarantees.

# Architecture

## Starting brief

Build a local MCP (Model Context Protocol) server in TypeScript that gives an AI agent working tools for my own SaaS accounts, using personal access tokens. No hosted service, no accounts, no telemetry.

Stack, non-negotiable:
- Node 20+, TypeScript, pnpm
- @modelcontextprotocol/sdk over stdio transport
- zod for tool input schemas
- undici fetch for HTTP, no per-provider SDKs

Structure:
- src/index.ts: server bootstrap, registers every tool module
- src/providers/gmail.ts, slack.ts, github.ts, notion.ts
- src/http.ts: one shared request helper with timeout, retry on 429 and 5xx with exponential backoff, and error normalization
- .env.example listing every token var, .env gitignored, fail loudly at startup if a token for an enabled provider is missing

Tools to implement, keep them small and honest:
- gmail_search_messages, gmail_get_message, gmail_send_message
- slack_list_channels, slack_post_message, slack_search_messages
- github_list_issues, github_create_issue, github_comment_issue
- notion_search, notion_get_page, notion_append_block
Each tool: zod-validated input, a one-line description an LLM can act on, and output trimmed to useful fields only, never raw API dumps.

In scope: static token auth, a PROVIDERS env var to enable a subset, structured logging to stderr only (stdout is the MCP channel), a vitest suite that mocks HTTP and covers happy path plus 401 and 429 handling.
Out of scope: OAuth flows, multi-user credential storage, a web UI, a database. Say so in the README.

Deliver a README with setup steps, token scope requirements per provider, and the exact JSON block to paste into a Claude Desktop or Cursor MCP config.

## Boundaries

Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors.

## Production baseline

- Configuration: validated at startup with safe local defaults where possible.
- Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives.
- Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions.
- Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts.
- Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists.
- Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test.

## Decision records

For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it.

# Agent instructions

- Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code.
- Implement milestone by milestone; keep each change reviewable and leave the application runnable.
- Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present.
- Never invent cryptography or silently weaken a requirement to make a test pass.
- Use provider interfaces for external services and deterministic fakes in tests.
- Add migrations and rollback or recovery notes for persistent data changes.
- Log useful operational context without credentials, tokens, passwords, or personal data.
- Update documentation and run all checks before completing a milestone.

# Delivery milestones

## M0 — Decisions and scaffold

- Confirm the runtime, persistence model, threat boundaries, and deployment target.
- Create a reproducible local environment and continuous checks.

## M1 — Core workflow

- Implement the smallest end-to-end product path with validation and tests.
- Keep integrations behind interfaces.

## M2 — Trust layer

- Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards.
- Test abuse cases and destructive operations.

## M3 — Operability

- Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration.

## M4 — Release gate

- Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise.
- Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations.

# Operations

## Before release

- Validate configuration and secrets at startup.
- Define backup, restore, and rollback procedures and test them.
- Document logs, error tracking, health signals, and alert ownership.
- Set dependency update and vulnerability review expectations.

## Incident checklist

1. Contain the issue without destroying evidence or user data.
2. Record the timeline and affected scope.
3. Rotate exposed secrets and revoke compromised sessions or credentials.
4. Restore from a verified source when needed.
5. Document the root cause, remediation, and regression test.

## Launch constraint

Do not market omitted Composio capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.

$ choose a build depth, inspect the files, then open the complete pack in your agent · this prompt is generated from the build plan · improve it via PR