Documentation

Everything you need to integrate DayBy into your workflow.

MCP Server

New

Post your dev progress directly from Claude Code, Claude Desktop, or Cursor. Content is sanitized locally before anything leaves your machine. API keys, tokens, IPs, and SSH keys are stripped automatically.

1. Install

Global install:

npm install -g @dayby/mcp-server

Or skip the install and run directly with npx:

npx -y @dayby/mcp-server

Or straight from GitHub:

npx github:ja-roque/dayby-mcp-server

2. Connect your account

Run this once in your terminal. It opens DayBy in the browser — just click Authorize. No API key needed.

dayby-mcp auth

Credentials are saved to ~/.dayby/credentials.json and picked up automatically. Run dayby-mcp auth --logout to disconnect.

Use an API key instead (legacy)

Go to Settings → API, enable API access, and create a key. Then set the env var:

export DAYBY_API_KEY=dyb_your_token_here

3a. Claude Code (terminal)

If you did the global install:

claude mcp add dayby -- dayby-mcp

Or with npx (no install needed):

claude mcp add dayby -- npx -y @dayby/mcp-server

3b. Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json:

{ "mcpServers": { "dayby": { "command": "npx", "args": ["-y", "@dayby/mcp-server"] } } }

Credentials from dayby-mcp auth are picked up automatically.

3c. Cursor

Edit ~/.cursor/mcp.json:

{ "mcpServers": { "dayby": { "command": "npx", "args": ["-y", "@dayby/mcp-server"] } } }

Credentials from dayby-mcp auth are picked up automatically.

Available Tools

draft_post

title, content

Create a draft. Content is sanitized locally before upload.

publish_post

slug

Publish an existing draft by slug.

edit_draft

slug, title?, content?

Update title or content of an existing draft.

check_content

content

Scan content for secrets without posting anything.

list_posts

List your recent posts and drafts.

Local sanitization

Strips API keys, tokens, IPs, SSH keys, JWTs, AWS ARNs, and database URLs from content before it leaves your machine. No LLM involved. Pure regex, offline, deterministic.

View source on GitHub →

REST API Reference

Full interactive docs with request/response schemas, try-it-out, and examples.

Open API Reference (Swagger UI)

Authentication

Pass your API key as a Bearer token on every request:

curl https://javier.dayby.dev/api/v2/posts \
-H "Authorization: Bearer dyb_your_token_here"

Rate limit: 60 requests/minute per key.