Skip to main content
Glama
developer-presence-mcp

developer-presence-mcp

developer-presence-mcp

An MCP server that connects your GitHub and DEV.to profiles to Claude (or any MCP client). Query your repos, stats, and articles — or create and publish new DEV.to posts — all from a conversation.

Built with FastMCP · Python stdlib only for HTTP · No heavy dependencies.

Tools

GitHub

Tool

Description

get_github_profile

Followers, repos, bio

list_repos

Public repos sorted by updated/stars/forks

get_repo_stats

Stars, forks, watchers, open issues for a repo

DEV.to

Tool

Description

list_articles

Your published articles with reaction/view counts

create_article

Draft or publish a new article

update_article

Edit title, body, or publish state

get_article_stats

Reactions, comments, page views for an article

Related MCP server: GitHub Assistant MCP Server

Setup

1. Clone and install

git clone https://github.com/enjoykumawat/developer-presence-mcp
cd developer-presence-mcp
pip install -r requirements.txt

2. Create .env

cp .env.example .env
# Fill in your credentials

Get your keys:

3. Run

# Dev mode with MCP Inspector
mcp dev server.py

# Or directly
python server.py

Claude Desktop

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "developer-presence": {
      "command": "python",
      "args": ["/path/to/developer-presence-mcp/server.py"],
      "env": {
        "GITHUB_TOKEN": "your_token",
        "GITHUB_USERNAME": "your_username",
        "DEV_TO_API": "your_devto_key",
        "DEV_USERNAME": "your_devto_username"
      }
    }
  }
}

Example prompts

Once connected to Claude:

"Show me my most starred GitHub repos"

"Draft a DEV.to article about my latest project and publish it"

"How many reactions did my last article get?"

"List my repos sorted by stars"

Author

Built by @enjoykumawat — AI agent tooling contributor, MCP python-sdk contributor.

Available Tools

7 tools
create_articleC

Create a new DEV.to article. Returns id and url.

Inputs: title (required), body_markdown (required), tags, published.

get_article_statsC

Get reactions, comments, and page views for a DEV.to article.

Inputs: article_id (required).

get_github_profileB

Fetch public GitHub profile stats.

Inputs: no named parameters.

get_repo_statsB

Get stars, forks, watchers, open issues for a repo.

Inputs: repo (required).

list_articlesC

List your published DEV.to articles.

Inputs: per_page.

list_reposB

List public repos. sort: updated|stars|forks. limit: 1-100.

Inputs: sort, limit.

update_articleC

Update an existing DEV.to article by id.

Inputs: article_id (required), title, published, body_markdown.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.1/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct entity or action: repos, articles, and profile. list_repos and get_repo_stats are clearly separate (list vs stats), and article tools cover create, update, list, and stats without ambiguity.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with lowercase and underscores (e.g., list_articles, create_article, get_repo_stats). The naming is predictable and clear.

    Tool Count5/5

    7 tools cover two logical domains (GitHub repos and DEV.to articles) without being too many or too few. Each tool serves a distinct purpose within the scope of developer presence.

    Completeness3/5

    The tool set covers basic operations for articles (list, create, update, stats) but lacks delete. For repos, only list and stats are available; missing individual repo details. Minor gaps affect core workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers