Developer Name
A lightweight Node.js server that serves customizable developer profile information and contact details through a simple command-line interface.
Provides customizable developer information through a lightweight Node.js server that can be run via npx command or deployed as a Docker container.
What it does
- Serve developer profile information via HTTP
- Run instantly with npx command
- Deploy as Docker container
- Customize developer contact details
- Access profile data programmatically
Best for
About Developer Name
Developer Name is a community-built MCP server published by seriawei that provides AI assistants with tools and capabilities via the Model Context Protocol. Developer Name offers customizable dev info through a lightweight Node.js server, easily run via npx or as a Docker cont It is categorized under developer tools.
How to install
You can install Developer Name in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
License
Developer Name is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
MCP-Server
It is use to return the current developer informations.
{
"mcpServers": {
"developer-name": {
"command": "npx",
"args": [
"-y",
"mcp-developer-name"
],
"env": {
"DEVELOPER_NAME": "Wayne Wei"
},
"disabled": false,
"autoApprove": []
}
}
}
Alternatives
Related Skills
Browse all skillsUI design system toolkit for Senior UI Designer including design token generation, component documentation, responsive design calculations, and developer handoff tools. Use for creating design systems, maintaining visual consistency, and facilitating design-dev collaboration.
Guide for building TypeScript CLIs with Bun. Use when creating command-line tools, adding subcommands to existing CLIs, or building developer tooling. Covers argument parsing, subcommand patterns, output formatting, and distribution.
Use when working with the OpenAI API (Responses API) or OpenAI platform features (tools, streaming, Realtime API, auth, models, rate limits, MCP) and you need authoritative, up-to-date documentation (schemas, examples, limits, edge cases). Prefer the OpenAI Developer Documentation MCP server tools when available; otherwise guide the user to enable `openaiDeveloperDocs`.
Master API documentation with OpenAPI 3.1, AI-powered tools, and modern developer experience practices. Create interactive docs, generate SDKs, and build comprehensive developer portals. Use PROACTIVELY for API documentation or developer portal creation.
Edit opencode.json, AGENTS.md, and config files. Use proactively for provider setup, permission changes, model config, formatter rules, or environment variables. Examples: - user: "Add Anthropic as a provider" → edit opencode.json providers, add API key baseEnv var, verify with opencode run test - user: "Restrict this agent's permissions" → add permission block to agent config, set deny/allow for tools/fileAccess - user: "Set GPT-5 as default model" → edit global or agent-level model preference, verify model name format - user: "Disable gofmt formatter" → edit formatters section, set languages.gofmt.enabled = false
Persistent long term memory for for continuity in ai sessions between providers and codegen tools. TRIGGERS - Activate this skill when: - User explicitly mentions "satori", "remember this", "save", "add", "save this for later", "store this", "add to memory" - User asks to recall/search past decisions: "what did we decide", "remind me", "search my notes", "what do I know about" - Conversation contains notable facts worth persisting: decisions, preferences, deadlines, names, tech stack choices, strategic directions - Starting a new conversation where proactive context retrieval would help - Use Satori search when user asks a question