Skip to main content

meteor-mcp

PyPI

In development

This package is published so the name is held while the work is planned in the open. It registers one tool, get_version_info, and does nothing else yet. If you install it expecting a working server, that is what you will find — which is why it says so here, in the server's own instructions, and in the one tool it has.

PyPI does not reserve a name for a pending trusted publisher, so a name is only held once something is actually published. Given that, a package that says what it is beats an empty one that does not.

Shower timing and radiant elevation computed locally, plus live meteor flux from the Global Meteor Network and recent fireballs from NASA CNEOS. Shower identity comes from the IAU Meteor Data Center, which names and numbers them; the annual calendar of peaks and rates comes from the IMO.

Planned work, including the data sources it would use and whether each is actually available, is tracked in qso-graph-devel#51.

Part of the qso-graph project.

Install

uvx meteor-mcp            # run it; nothing to install

Tools

Tool Description
get_version_info Service version, development status, and where the work is tracked

Quick Start

No credentials needed — install and configure your MCP client.

Configure your MCP client

meteor-mcp works with any MCP-compatible client. Add the server config and restart.

Claude Desktop

Add to claude_desktop_config.json (~/Library/Application Support/Claude/ on macOS, %APPDATA%\Claude\ on Windows):

{
  "mcpServers": {
    "meteor": {
      "command": "uvx",
      "args": ["meteor-mcp"]
    }
  }
}

Claude Code

Add to .claude/settings.json:

{
  "mcpServers": {
    "meteor": {
      "command": "uvx",
      "args": ["meteor-mcp"]
    }
  }
}

ChatGPT Desktop

Configure via Settings > Apps & Connectors, or in your agent definition:

{
  "mcpServers": {
    "meteor": {
      "command": "uvx",
      "args": ["meteor-mcp"]
    }
  }
}

Questions it will answer

Not yet — these are what the finished server is for:

"Which meteor showers are active this week, and when do they peak?"

"When is the Perseid radiant highest from my grid square?"

"What is the meteor rate right now?"

Licence

GPL-3.0-or-later. See LICENSE.

Metadata

Release files for meteor-mcp 0.0.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for meteor-mcp 0.0.1
File Size Uploaded
meteor_mcp-0.0.1.tar.gz 170.3 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for meteor-mcp 0.0.1
File Interpreter ABI Platform
meteor_mcp-0.0.1-py3-none-any.whl Python 3 none any Details

Total release size: 186.9 kB

Release files / meteor_mcp-0.0.1.tar.gz

Download URL meteor_mcp-0.0.1.tar.gz
Size 170.3 kB
Tags Source
SHA-256 checksum
How to use checksums
19860f2b73f42a0b2327bca99579807ac9670c14f97d866d8a0b0c302fa7d55a
BLAKE2b-256 checksum
How to use checksums
2992973d14ede1a6befc2b52617b79a6e363dbd4df3071fd73f7e2d7808053f9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 11, 2026.

Transparency log

Release files / meteor_mcp-0.0.1-py3-none-any.whl

Download URL meteor_mcp-0.0.1-py3-none-any.whl
Size 16.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
ab794e984cc2e947a6f268de31dbec7e784e617bb4d26f263aea0386a9115f3c
BLAKE2b-256 checksum
How to use checksums
191a61166225ac6f9ee6c9178cc42fd767f9130976832f426d31d36e302afd35
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 11, 2026.

Transparency log

Release history Release notifications | RSS feed

0.1.0

2 release files

This release

0.0.1 This release

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page