modelcontextprotocol / modelcontextprotocol/servers

confusing documentation

Open
#521 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

I have an application that expects mcp to be on port 3001 over sse. the documentation tells me how to create the config.json alright, but then it goes into if I want to make a server, or a client, or this or that which I do not want to do. what I want to do is to run mcp so it's available at that port, but I'm not even sure what to run. the documentation doesn't even really go into anything useful. somehow I stumbled on the model inspector

image

it also seems to be able to talk to mcp on port 3001, but no dice. where is the binary? what do I run? where do I set the port? do I make a systemd service to start something? how does mcp run? in fact I don't even know where to put the config.json.

on the git page I see "For example, this will start the Git server:

With uvx

uvx mcp-server-git" but running uvx mcp-server-git doesn't seem to do anything, there is no output, there are no ports opened.... it just sits there.

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 reviewing the existing config.json guidance and the Git server's uvx example, then verify how the server is started and exposed over SSE. Update the documentation to explain the executable or command, config.json location, port configuration, and whether a service is needed, with a working port-3001 example as the done criteria.

Written by the indexing model from the issue text.

Assessment

Domain
cli, documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.