developer-presence-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEV_TO_API | Yes | DEV.to API key from dev.to/settings/extensions | |
| DEV_USERNAME | Yes | DEV.to username | |
| GITHUB_TOKEN | Yes | GitHub personal access token with repo and user scopes | |
| GITHUB_USERNAME | Yes | GitHub username |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_github_profileB | Fetch public GitHub profile stats. |
| list_reposB | List public repos. sort: updated|stars|forks. limit: 1-100. |
| get_repo_statsB | Get stars, forks, watchers, open issues for a repo. |
| list_articlesC | List your published DEV.to articles. |
| create_articleC | Create a new DEV.to article. Returns id and url. |
| update_articleC | Update an existing DEV.to article by id. |
| get_article_statsC | Get reactions, comments, and page views for a DEV.to article. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
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.
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.
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.
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.