Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Who's in Space who's in space right now?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A tiny Model Context Protocol server that lets an AI assistant answer "who is in space right now?" and "where is the ISS?" using the free, no-API-key Open Notify service.
Great as a first MCP demo: two live tools, zero credentials, always-changing data. It also ships a live web map of both crewed space stations (see below).
🌐 Live map (GitHub Pages): https://andresapitt.github.io/ceai-mcp-iss/
Tool | Arguments | Returns |
| none | People currently in orbit, grouped by spacecraft |
| none | Live latitude/longitude of the ISS + a map link |
| none | A composed summary (people + ISS position) from both sources — the "customer briefing" pattern |
Related MCP server: astronomy-mcp-server
npm install
npm run buildA web page that plots both crewed space stations — the ISS and China's Tiangong (CSS) — on a world map. Hover a marker to see who's on board. Each station has a coloured fading trail and the positions update every second.
npm run web
# then open http://localhost:3000How it works:
web/server.mjs serves the page and proxies two free, no-key sources
server-side (so the browser never hits a CORS wall):
Open Notify (/api/astros — who is on each craft) and CelesTrak
(/api/tle?id=… — each station's orbital elements, cached for an hour).
The browser computes each station's live ground position from its orbital elements using satellite.js, so the markers move smoothly every second without polling any API.
Map is Leaflet + OpenStreetMap. All libraries load from a CDN; everything is
free and key-less. Set a different port with PORT=8080 npm run web.
GitHub Pages only serves static files over HTTPS — it can't run the Node
proxy in web/server.mjs. So a static build lives in docs/ that talks
to the data sources directly:
Positions are fetched straight from CelesTrak (HTTPS + open CORS), so the map stays fully live.
Crew comes from a committed snapshot, docs/crew.json,
because Open Notify is HTTP-only and a browser on an HTTPS page blocks it as
"mixed content". Crew changes only every few months.
Enable it (one time): repo Settings → Pages → Build and deployment →
Source: Deploy from a branch → Branch: main, folder: /docs → Save.
After a minute the site is live at
https://andresapitt.github.io/ceai-mcp-iss/.
To refresh the crew snapshot (e.g. after a crew rotation):
curl -s http://api.open-notify.org/astros.json -o docs/crew.json
git commit -am "Update crew snapshot" && git pushThe MCP server itself cannot run on Pages — it's a stdio process an AI client launches, not a web page. Pages hosts only the visual map.
There are two ways to run it.
npm run demoThis launches the server, discovers the tools, calls each one, and prints the
live results. Uses the small MCP client in demo.mjs. Great for a quick
"it works" check or a screen-share where you narrate each tool call.
(npm start is also available — it starts the server on stdio and waits for
raw JSON-RPC on stdin, for manual testing.)
This is the version to present — you ask Claude a question and it calls your tool. See the next section for setup, then ask:
"Who's in space right now?"
"Where is the ISS?"
"Give me a space briefing"
Claude shows a "used tool" indicator and answers from the live data.
Presenting tips
Run a query twice — the ISS coordinates change every time, proving it's a real live tool and not the model guessing.
Keep a terminal with npm run demo open as a backup in case Claude Desktop is
slow to reconnect.
Add this to your claude_desktop_config.json
(Windows: %APPDATA%\Claude\claude_desktop_config.json):
{
"mcpServers": {
"whos-in-space": {
"command": "node",
"args": [
"C:\\Users\\andre\\OneDrive - vStream\\Documents\\Andrés\\courses\\AI in Business\\Customer Engagement and AI\\projects\\mcp\\dist\\index.js"
]
}
}
}Steps:
Edit the config file above (on Windows, run
notepad "$env:APPDATA\Claude\claude_desktop_config.json" in PowerShell).
Merge the whos-in-space entry into any existing mcpServers — don't delete
what's already there.
Fully quit Claude Desktop (File → Exit, not just closing the window) and reopen it, so it restarts the background process.
Click the tools/plug icon in the chat box — you should see whos-in-space
with 3 tools.
Ask "Who's in space right now?"
If the tools don't appear: recheck the path (double backslashes \\) and make
sure npm run build has been run so dist\index.js exists.
npx (no dist path to hardcode)After npm run build, you can let the client run the package by folder instead
of pointing at dist/index.js:
{
"mcpServers": {
"whos-in-space": {
"command": "npx",
"args": [
"C:\\Users\\andre\\OneDrive - vStream\\Documents\\Andrés\\courses\\AI in Business\\Customer Engagement and AI\\projects\\mcp"
]
}
}
}npx <folder> resolves the bin entry in package.json and runs it.
src/index.ts creates an McpServer, registers two tools, and speaks the MCP
protocol over stdio (stdout = protocol, stderr = logs).
Each tool does a single fetch to Open Notify and formats the result as text.
No API key, no auth, no rate-limit signup.
MIT © 2026 Andrés Apitt
Returns the current latitude and longitude of the International Space Station. Live data, no arguments needed.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'Live data' but does not disclose factors like update frequency, accuracy, or any potential limitations. This is minimal for a tool relying solely on its description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise with two short sentences, each carrying essential information. It is front-loaded with the purpose and includes only necessary details, making it efficient for an AI agent to parse.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's low complexity (zero parameters, simple output), the description is adequate but has gaps: it does not specify the coordinate format (e.g., degrees) or whether the data is cached. The lack of output schema and annotations limits completeness, but the description covers the core functionality.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters and the schema coverage is 100% (empty properties). The description adds value by explicitly stating 'no arguments needed', confirming that no input is required, which aligns with the baseline score of 4 for zero-parameter tools.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'returns' and the specific resource 'current latitude and longitude of the International Space Station'. This distinguishes it from sibling tools like space_briefing and whos_in_space, which cover different aspects of ISS data.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description indicates when to use the tool (when you need live ISS location) and explicitly says 'no arguments needed', providing clear usage guidance. However, it does not explicitly state when not to use it or mention alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Produces a short, ready-to-read briefing that combines who is currently in space with the live position of the ISS. Live data, no arguments needed.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, but the description discloses it is a read-only, no-argument tool. It could mention data freshness or error handling, but for a simple briefing tool it is adequate.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One sentence, front-loaded with key purpose and data sources. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simplicity and lack of output schema, the description is sufficient. It could specify the output format but is not required.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters exist, so schema coverage is 100%. The description adds no parameter info, but none is needed.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool produces a briefing combining who is in space and ISS location. It distinguishes from sibling tools (iss_location, whos_in_space) by being a combined output.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description says 'no arguments needed' and implies it's a convenience tool. It doesn't explicitly say when to use this vs the individual siblings, but the context makes it clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Returns the people who are currently in space right now and which spacecraft each one is aboard. Live data, no arguments needed.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It mentions 'live data' and 'no arguments needed', which is adequate for a simple read-only tool. No additional behavioral traits are needed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence, concise, and front-loaded with the key information. Every word is necessary.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema and no annotations, the description is complete enough for a simple tool. It could mention the output format, but not necessary for understanding the tool's purpose.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There are no parameters, and the schema coverage is 100%. The description adds that no arguments are needed, reinforcing the schema. Baseline for 0 parameters is 4.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool returns people currently in space and their spacecraft, using specific verb 'Returns' and resource. It distinguishes from sibling tools like iss_location and space_briefing.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description says 'no arguments needed', providing clear context for usage. However, it does not explicitly state when to use this tool versus alternatives, but the context is sufficient for a simple tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
v1.0.0iss_locationspace_briefingwhos_in_spaceEach tool has a clearly distinct purpose: iss_location returns coordinates, whos_in_space returns astronaut list, and space_briefing combines both. No overlap or ambiguity.
All tool names use snake_case and follow a clear pattern: 'iss_location' (noun), 'whos_in_space' (question phrase), 'space_briefing' (noun). The naming is predictable and descriptive.
Three tools is perfectly scoped for a server covering ISS location and people in space. Each tool is necessary and non-redundant. The count is appropriate.
The tool set fully covers the core functionality: location, people, and a combined briefing. No obvious gaps given the server's focused purpose.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Open Notify MCP — ISS position + people in space
Live space data for AI agents - rocket launches, ISS passes, launch news. Free, no auth.
iss-number MCP — wraps StupidAPIs (requires X-API-Key)
Read and update your Everway trips and itineraries from any MCP-compatible AI assistant.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/andresapitt/ceai-mcp-iss'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
