# Tempo Atlas Projects MCP server
> Search Tempo ecosystem projects, read project details and list categories from the TempoAtlas directory.
- Listing: https://mcp.tc/i/tempo-atlas-projects
- Connect: use the server's own URL `https://tempoatlas.net/mcp` (no sign-in); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: none
- Category: [Docs & Knowledge](https://mcp.tc/c/docs-knowledge)
- Vendor: TempoAtlas
- Homepage:
## About
Connects to TempoAtlas, an independent, sourced reference for the Tempo payments blockchain ecosystem. You can search published projects by name, description or tag, fetch a project by its slug with its public links, and list categories with project counts.
Runs as a hosted Streamable HTTP endpoint at https://tempoatlas.net/mcp. It is read-only and needs no sign-in or API key. Listings are informational and not investment advice.
## What it can do
- Search Tempo ecosystem projects by name, description or tag
- Filter project searches by category with paging
- Retrieve a project by slug with description and public links
- List categories with published project counts
## Tools (3)
- `search_projects`: Search published projects by name, description or tag, with category, limit and offset options. (read-only)
- `get_project`: Retrieve a published project by exact slug, with description and public links. (read-only)
- `list_project_categories`: List categories and their published project counts. (read-only)
## Example prompts
- "Search Tempo Atlas for stablecoin projects on Tempo."
- "Show the details for the Morpho project on Tempo Atlas."
- "List all project categories in the Tempo ecosystem."
- "Browse wallet and custody projects listed on Tempo Atlas."
## Install
### Claude Code
1. Run this in a terminal, in your project folder:
```bash
claude mcp add --transport http tempo-atlas-projects https://tempoatlas.net/mcp
```
2. Start Claude Code and type `/mcp`. **tempo-atlas-projects** should show as connected.
Add `--scope user` to make it available in every project, not just this one.
### Claude Desktop
1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.
2. Name it **Tempo Atlas Projects** and paste this URL:
```url
https://tempoatlas.net/mcp
```
3. Click **Add**. Its tools appear in the chat’s tools menu.
Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.
### claude.ai
1. Open the connector form on claude.ai. This button fills in the name and URL for you:
[Add to claude.ai]() (opens connector settings)
2. Check that the URL reads `https://tempoatlas.net/mcp` and click **Add**.
3. Turn it on in a chat from the tools menu.
Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.
### ChatGPT
1. On chatgpt.com, go to **Plugins**, select **+**, then **Add custom MCP server**.
2. Enter a name for the server.
3. Under **Connection**, paste `https://tempoatlas.net/mcp` as the server URL, then for authentication choose **No authentication**.
4. Check **I understand and want to continue**, then select **Create as a plugin**.
Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).
### Cursor
[Add to Cursor]() (opens Cursor)
Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):
`mcp.json`:
```json
{
"mcpServers": {
"tempo-atlas-projects": {
"url": "https://tempoatlas.net/mcp"
}
}
}
```
### VS Code
[Install in VS Code]() (opens VS Code)
Or from a terminal:
```bash
code --add-mcp '{"name":"tempo-atlas-projects","type":"http","url":"https://tempoatlas.net/mcp"}'
```
Or commit it to the repo in `.vscode/mcp.json`:
`.vscode/mcp.json`:
```json
{
"servers": {
"tempo-atlas-projects": {
"type": "http",
"url": "https://tempoatlas.net/mcp"
}
}
}
```
### Devin Desktop
1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):
`mcp_config.json`:
```json
{
"mcpServers": {
"tempo-atlas-projects": {
"serverUrl": "https://tempoatlas.net/mcp"
}
}
}
```
2. Refresh the MCP server list in Cascade.
Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.
### Codex
```bash
codex mcp add tempo-atlas-projects --url https://tempoatlas.net/mcp
```
Or edit `~/.codex/config.toml` directly:
`config.toml`:
```toml
[mcp_servers.tempo-atlas-projects]
url = "https://tempoatlas.net/mcp"
```
### Gemini CLI
```bash
gemini mcp add --transport http tempo-atlas-projects https://tempoatlas.net/mcp
```
This adds it to the current project. Add `-s user` to use it everywhere.
### Any client
Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.
```json
{
"mcpServers": {
"tempo-atlas-projects": {
"type": "http",
"url": "https://tempoatlas.net/mcp"
}
}
}
```
Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.
Client only starts local servers? Bridge it with `npx -y mcp-remote https://tempoatlas.net/mcp`.
## Recent changes
- 2026-10-26 17:31 UTC: Tracking started: 3 tools read. Source: automatic check.
More on the History tab, with descriptions before and after for the newest entries: https://mcp.tc/i/tempo-atlas-projects#history (Atom feed: https://mcp.tc/i/tempo-atlas-projects/history.xml). It records what mcp.tc's anonymous checks saw, every 3 hours where the tool list can be read without sign-in; it is not a security review.
## Details
- Server version: 1.0.0
- MCP protocol version: 2026-07-28
- Last checked: 2026-11-14 (reachable)
- Listed: 2026-10-26
- Updated: 2026-10-26
---
Source: https://mcp.tc/i/tempo-atlas-projects (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report