modelcontextprotocol / modelcontextprotocol/servers

[Feature]: Unify the names of the Time MCP server tools

Open
#3,201 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
90.5k
Forks
11.7k
Avg merge
2d 2h
Merged PRs (30d)
5

Description

Hey!

I'm using the Time MCP server via the Docker MCP Toolkit.

Most MCPs with multiple tools available have a prefix for them.

But Time's tool is registered without one.

Looking at the available tools, I can see several MCP-related tools:

  1. MCP_DOCKER_browser_* - Browser automation tools (click, navigate, snapshot, etc.)
  2. MCP_DOCKER_code-mode - Create JavaScript-enabled tools combining multiple MCP servers
  3. MCP_DOCKER_convert_time - Timezone conversion
  4. MCP_DOCKER_fetch - Fetch URLs from internet
  5. MCP_DOCKER_get-library-docs - Fetch library documentation
  6. MCP_DOCKER_get_current_time - Get current time in timezone
  7. MCP_DOCKER_git_* - Git operations (add, checkout, commit, diff, etc.)
  8. MCP_DOCKER_mcp-* - MCP server management (find, add, remove, config, etc.)
  9. MCP_DOCKER_resolve-library-id - Resolve package names to library IDs
  10. MCP_DOCKER_sequentialthinking - For complex problem solving

Is it possible to add a 'time_' prefix to make similar tools easier to identify, coming from a single MCP server?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the Time MCP server's tool registration and any associated tests. Rename the tools so both use the requested time_ prefix, and confirm the resulting names are consistent wherever the tools are exposed.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
tooling
Issue type
Feature
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.