Skip to main content
Glama
deenesjakoruzh
odddman44

DevLog MCP

by odddman44
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

DevLog MCP

Это stdio MCP-сервер, который публикует журналы разработки, написанные AI-агентами кодирования, такими как Codex, Claude Code, в существующую базу данных Notion Blog. Агент отвечает за ретроспективу и написание текста, а этот сервер отвечает только за проверку ввода и сохранение в Notion.

Требования

  • Node.js 20 или выше

  • Существующая база данных Notion Blog

  • Notion Integration, подключенная к базе данных

Related MCP server: Relentless MCP Server

Установка и сборка

npm install
npm test
npm run build

При непосредственном запуске во время разработки установите переменные окружения в текущей оболочке. Этот проект не читает файл .env автоматически.

export NOTION_TOKEN="secret_..."
export NOTION_DATABASE_ID="..."
npm run dev

Поскольку stdio-сервер общается с MCP-клиентом через JSON-RPC, при запуске в терминале не выводится обычное приветственное сообщение.

Настройка Notion

  1. Создайте внутреннюю интеграцию на странице Integrations в Notion.

  2. Используйте токен интеграции как NOTION_TOKEN.

  3. В меню подключений существующей базы данных блога добавьте эту интеграцию.

  4. Найдите ID базы данных в URL базы данных и используйте его как NOTION_DATABASE_ID.

Имена и типы свойств базы данных должны быть следующими:

Свойство

Тип Notion

Значение по умолчанию

Title

Title

Обязательное поле

Category

Select

Разработка

Tags

Multi-select

Пустой список

PublishedAt

Date

Текущая дата

Status

Status

published

Если переданное имя отсутствует в параметрах 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, абзацы, упорядоченные/неупорядоченные списки, блоки кода с ограждением, разделители.

Пример входных данных для вызова:

{
  "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 list

Подключение Claude 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 tool
publish_dev_log개발 일지 발행B

완성된 개발 일지를 기존 Notion Blog DB에 발행합니다.

ParametersJSON Schema
NameRequiredDescriptionDefault
tagsNo글 내용을 나타내는 태그
titleYes개발 일지 제목
statusNo발행 상태
contentYesMarkdown 형식의 개발 일지 본문
categoryNo카테고리. 기본값은 개발
publishedAtNo발행일. 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. Dates show when Glama detected each change.

  1. 1 tool updatev0.1.0
    • First observedpublish_dev_log
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.4/5.0
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

ActivityMaintained
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/odddman44/devlog-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server