@dayby/mcp-server

Write, publish, and manage blog posts on DayBy.dev from Claude, Cursor, or any MCP client — with built-in content sanitization so your secrets never leave your machine.

Two Ways to Connect

Option A: claude.ai / Web / Mobile (no install)

Use DayBy as a remote MCP connector — no local setup needed. Works from claude.ai, the Claude mobile app, or any client that supports remote MCP servers.

1. Sign up at dayby.dev
2. Go to Settings > API, enable API access, and create a key
3. In claude.ai, go to Settings > Integrations > Add custom connector
4. Set the URL to: https://dayby.dev/mcp/server
5. Set auth to Bearer token and paste your API key

That's it. Start a conversation and ask Claude to draft and publish a post.

Option B: Claude Code / Desktop / Cursor / Codex (local, more private)

Use the local MCP server for maximum privacy. Content is sanitized on your machine before anything touches the network.

Install:

npm install -g @dayby/mcp-server

Authenticate:

dayby-mcp auth

Opens DayBy in the browser — click Authorize. Token is saved to ~/.dayby/credentials.json automatically.

Add to your tool:

Claude Code:

claude mcp add dayby -- dayby-mcp

Codex:

codex mcp add dayby -- dayby-mcp

Cursor / Claude Desktop (JSON config):

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

Tools

| Tool | What it does | |---|---| | draft_post | Create a sanitized draft from your content | | edit_draft | Modify a draft before publishing | | publish_post | Publish a draft to DayBy (optionally generate an AI article) | | update_post | Update an existing post | | update_article | Set or replace the HTML article for a post | | check_content | Dry-run: see what would get stripped | | list_posts | List your recent posts | | get_post | Get a single post by slug | | delete_post | Permanently delete a post |

What Gets Stripped (Automatically)

• API keys, tokens, secrets
• AWS ARNs and access keys
• Private IP addresses
• Email addresses
• SSH keys, JWTs, GitHub tokens
• Database connection URLs
• File paths with usernames
• Plus anything you configure in blocklist (local mode only)

Configure Sanitizer Blocklist (Local Mode Only)

Create ~/.dayby/sanitizer.json:

{
  "blockedTerms": ["YourCompany", "ProjectCodename"],
  "blockedDomains": ["internal.yourcompany.com"],
  "blockedNames": ["Your Boss Name"],
  "customPatterns": ["JIRA-\\d+", "INTERNAL-\\d+"]
}

Usage Examples

While coding:

"I just figured out how to use PostgreSQL partial indexes to optimize a multi-tenant query. Draft a DayBy post about it."

After a PR:

"I built a rate limiter using Redis sorted sets today. Post it to DayBy."

Quick check:

"Check if this text has any sensitive data before I post it."

Claude will use draft_post to sanitize, show you a preview, and only publish when you approve.

Environment Variables

| Variable | Description | Default | |---|---|---| | DAYBY_API_KEY | Your DayBy API key | (required if not using dayby-mcp auth) | | DAYBY_API_URL | DayBy API URL | https://dayby.dev | | DAYBY_BLOCKED_TERMS | Comma-separated blocked terms | (none) | | DAYBY_BLOCKED_DOMAINS | Comma-separated blocked domains | (none) |

License

MIT