Tempo Atlas Projects

io.github.zeit-devPublished by GitHub account zeit-devv1.0.0Updated Oct 24, 2026

Search Tempo ecosystem projects, retrieve project details, and list categories.

The publisher's own server: Red Atlas Api

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

Lets an assistant search Tempo ecosystem projects, fetch individual project details, and list project categories through a hosted endpoint.

What you can do
This remote MCP server exposes the Tempo Atlas project directory to an assistant. According to its description, it supports searching Tempo ecosystem projects, retrieving details for a given project, and listing the available categories. It is a read-only lookup service for directory information rather than a tool that changes anything.
When to use it
Useful when you want an assistant to look up projects in the Tempo ecosystem, compare entries, or browse categories while researching or writing about that ecosystem. It adds little if you do not need Tempo project directory data.
Requirements
A remote streamable HTTP MCP endpoint at No packages, environment variables, or headers are declared, and no authentication is declared, so network access to the endpoint is the main requirement.
Before you install
No credentials, payments, or write actions are declared. Queries are sent to a third-party hosted service, so search terms and requests leave your machine; treat returned project information as third-party content and verify anything important at the source.

Installation

In SourceWeft

  1. Open Tempo Atlas Projects in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.zeit-dev%2Ftempoatlas-projects/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "tempo-atlas-projects": {
      "type": "http",
      "url": "https://tempoatlas.net/mcp"
    }
  }
}

Tools

3

search_projects

Search published Tempo Atlas projects by name, description or tag. An empty query browses the directory. Results are ordered by name and slug.

Parameterslimitqueryoffsetcategory

get_project

Retrieve a published project by its exact slug, including its description and public links.

Parametersslugrequired

list_project_categories

List categories and their published project counts. Use the exact category value with search_projects.

Takes no parameters.

Version history

1
  1. v1.0.0LatestOct 16, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Atlas integrations