A
licenseNot graded
qualityD
maintenanceEnables Language Models to interact with Notion workspaces through standardized tools for searching, reading, creating, and updating pages and databases.
119
MIT
DevLog MCP
by odddman44
DevLog MCP
Codex、Claude CodeなどのAIコーディングエージェントが作成した開発日誌を、既存のNotion Blog DBに発行するstdio MCPサーバーです。エージェントが振り返りと本文作成を担当し、このサーバーは入力検証とNotion保存のみを担当します。
要件
Node.js 20以上
既存のNotion Blog Database
Databaseに接続されたNotion Integration
Related MCP server: Notion MCP Server
インストールとビルド
npm install
npm test
npm run build開発中に直接実行する場合は、環境変数を現在のシェルに設定します。このプロジェクトは.envファイルを自動的に読み込みません。
export NOTION_TOKEN="secret_..."
export NOTION_DATABASE_ID="..."
npm run devstdioサーバーはMCPクライアントとJSON-RPCで通信するため、ターミナルで実行しても一般的な案内メッセージは出力されません。
Notion設定
NotionのIntegrations画面でInternal Integrationを作成します。
Integration tokenを
NOTION_TOKENとして使用します。既存のBlog Databaseの接続メニューで該当のIntegrationを追加します。
Database URLからDatabase IDを見つけ、
NOTION_DATABASE_IDとして使用します。
Databaseのプロパティ名とタイプは以下の通りである必要があります。
プロパティ | Notionタイプ | デフォルト値 |
| Title | 必須入力 |
| Select |
|
| Multi-select | 空のリスト |
| Date | 現在の日付 |
| Status |
|
既存のDatabaseのSelect、Multi-select、Statusオプションに渡した名前がない場合、Notionの権限と設定によってオプションの作成が制限される可能性があります。
MCPツール
サーバーはpublish_dev_logツールを一つ提供します。
type PublishDevLogInput = {
title: string;
category?: string;
tags?: string[];
publishedAt?: string;
status?: "published" | "draft";
content: string;
};本文でサポートするMarkdownは、見出し1〜3、段落、順序付き/順序なしリスト、fenced code block、区切り線です。
呼び出し入力例は以下の通りです。
{
"title": "DevLog MCP 첫 구현",
"tags": ["MCP", "Notion", "TypeScript"],
"content": "# 오늘의 작업\nNotion 발행 도구를 구현했다.\n\n## 결정\n- MCP는 저장만 담당한다.\n- 회고 작성은 코딩 에이전트가 담당한다."
}Codex接続
まず、絶対パス基準でビルド結果を登録します。
codex mcp add devlog-mcp \
--env NOTION_TOKEN=secret_... \
--env NOTION_DATABASE_ID=... \
-- node /Users/oddd/workspace/notion/devlog-mcp/dist/index.js登録状態は次のコマンドで確認します。
codex mcp listClaude Code接続
プロジェクトスコープのMCPサーバーとして登録します。
claude mcp add -s project devlog-mcp \
-e NOTION_TOKEN=secret_... \
-e NOTION_DATABASE_ID=... \
-- node /Users/oddd/workspace/notion/devlog-mcp/dist/index.js登録状態は次のコマンドで確認します。
claude mcp list接続後、エージェントに今日開発した内容を日誌にまとめてpublish_dev_logで発行してと依頼できます。
devlog-mcp
Available Tools
1 toolpublish_dev_log개발 일지 발행B
완성된 개발 일지를 기존 Notion Blog DB에 발행합니다.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tags | No | 글 내용을 나타내는 태그 | |
| title | Yes | 개발 일지 제목 | |
| status | No | 발행 상태 | |
| content | Yes | Markdown 형식의 개발 일지 본문 | |
| category | No | 카테고리. 기본값은 개발 | |
| publishedAt | No | 발행일. YYYY-MM-DD 형식 |
TDQS
B3.2/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden for behavioral disclosure. It only states the action (publish to DB) without mentioning idempotency, overwriting behavior, authentication needs, error conditions, or any side effects. This is insufficient for a mutation tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence that efficiently conveys the core action and target. Every word is meaningful, and there is no fluff or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the lack of output schema and annotations, and the presence of 6 parameters including an enum, the description does not provide enough context. It omits return values, error behavior, status effects, and operational prerequisites, leaving the agent underinformed.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the baseline is 3. The description adds no additional meaning to any parameter beyond what the schema already provides (e.g., format hints, defaults, or usage context).
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
Description states the verb 'publishes' and the resource 'completed development log' to the 'existing Notion Blog DB'. It is clear what the tool does, but with no sibling tools, differentiation is not applicable, so it scores 4 per rubric.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description includes '완성된' (completed), which implies the tool should be used when the development log is finished. However, it provides no explicit when-not-to-use instructions, prerequisites, or alternative tools, so guidance is only implied.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
v0.1.0- First observed
publish_dev_log
TDQS
B3.4/5.0
Scored across 1 tool
Disambiguation5/5
With only one tool, there is no possibility of confusion. The tool's purpose is entirely distinct by default.
Naming Consistency5/5
A single tool cannot violate any naming pattern. The name 'publish_dev_log' follows a clear verb_noun convention.
Tool Count3/5
A single tool for a server named 'DevLog MCP' feels thin. While it may serve a specific publishing need, the scope suggests more tools would be expected for full log management.
Completeness2/5
The tool only covers publishing completed logs. Missing basic operations like create, list, update, or delete dev logs, which are likely needed for a complete workflow.
Maintenance
ActivitySlowing
ResponsivenessNo issues
Related MCP Connectors
Publish to self-hosted WordPress from AI agents: markdown, images, SEO, and Notion sync.
Create, manage, publish, and analyze Inblog content through AI agents.
Instant blogs for AI agents: a publishing CMS with no dashboard. One signup call returns a blog, an API key and a live URL; then publish markdown posts and get public URLs back.
Database for your AI agent. Turn its output into data, docs, skills, and apps you can actually use.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with Notion workspaces through the Notion API, allowing them to search, read, create, update pages and databases, and manage comments using natural language commands.168,517 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to save and manage question-and-answer pairs within a structured Notion database. It provides tools for database setup, entry creation, and querying existing conversation history.2 npm1MIT
- AlicenseAqualityAmaintenanceEnables AI coding agents to store and retrieve durable project decisions, conventions, environment notes, and bug fixes in Notion, with optional Obsidian Vault dual-write.620 npmMIT