Llmstxt

by agents-mcp-hackathonco.huggingface.agents-mcp-hackathon/llmstxt

Access documentation in your IDE with llms.txt

  • Remote endpoint
  • 2 tools
  • APACHE-2.0

Uptime

Checked  · every day

100%from 4 days of checks

Up without downtime on 3 of 3 days with data.

  • No downtime
  • Degraded
  • Down over 5 minutes
  • No data
  • Not checked yet

Response time

Median 1025 ms, slowest 5% 1243 ms for the handshake and the tool list, over 30 days.

1500 ms750 ms0

How far each check got

  • Reached the address 100%
  • Completed the handshake 100%
  • Listed its tools 100%

2 tools at the last answer.

Every day
DayResultChecksMedian
3 Nov (today)No verdict yet0–
2 NovNo downtime1of 11027 ms
1 NovNo downtime1of 11167 ms
31 OctNo downtime21000 ms

A failure counts as down time only when a second check five minutes later fails too. How we check

Connect to the publisher's own endpoint

Add to mcp.json (Program › Install › Edit mcp.json):

{
  "mcpServers": {
    "llmstxt": {
      "url": "https://agents-mcp-hackathon-llmstxt.hf.space/gradio_api/mcp/sse"
    }
  }
}
For agents: the install prompt

Every step above as one Markdown text, for an assistant installing it for you.

# Install the MCP server Llmstxt (`co.huggingface.agents-mcp-hackathon/llmstxt`)

Its page: https://plug.directory/servers/co.huggingface.agents-mcp-hackathon/llmstxt

It runs on the publisher's servers; the client connects to its URL.

Use the section for the person's client.

## Claude Desktop

Paste into Settings › Connectors › Add custom connector:

```text
https://agents-mcp-hackathon-llmstxt.hf.space/gradio_api/mcp/sse
```

## Claude Code

Run in a terminal:

```sh
claude mcp add --transport sse llmstxt https://agents-mcp-hackathon-llmstxt.hf.space/gradio_api/mcp/sse
```

## Cursor, Devin Desktop, LM Studio, Gemini CLI, oterm, ECA

Merge into the place for the person's client:

- Cursor: ~/.cursor/mcp.json
- Devin Desktop: ~/.config/devin/mcp_config.json
- LM Studio: mcp.json (Program › Install › Edit mcp.json)
- Gemini CLI: ~/.gemini/settings.json
- oterm: config.json in oterm's data folder (~/Library/Application Support/oterm on macOS, ~/.local/share/oterm on Linux, %APPDATA%\oterm on Windows)
- ECA: ~/.config/eca/config.json (global) or .eca/config.json in the project

```json
{
  "mcpServers": {
    "llmstxt": {
      "url": "https://agents-mcp-hackathon-llmstxt.hf.space/gradio_api/mcp/sse"
    }
  }
}
```

## VS Code

Merge into .vscode/mcp.json:

```json
{
  "servers": {
    "llmstxt": {
      "type": "sse",
      "url": "https://agents-mcp-hackathon-llmstxt.hf.space/gradio_api/mcp/sse"
    }
  }
}
```

## Zed

This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.

## Cline, AnythingLLM, Augment Code

Merge into the place for the person's client:

- Cline: cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers)
- AnythingLLM: anythingllm_mcp_servers.json in the AnythingLLM storage plugins directory
- Augment Code: Augment Settings Panel – MCP section – Import from JSON (VS Code extension)

```json
{
  "mcpServers": {
    "llmstxt": {
      "type": "sse",
      "url": "https://agents-mcp-hackathon-llmstxt.hf.space/gradio_api/mcp/sse"
    }
  }
}
```

## Continue

Merge into ~/.continue/config.yaml:

```yaml
mcpServers:
  - name: "llmstxt"
    type: sse
    url: "https://agents-mcp-hackathon-llmstxt.hf.space/gradio_api/mcp/sse"
```

## Goose

This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.

## Codex

This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.

## mcp-client-cli, TUUI, BoltAI, Bob Shell, Kiro, Kiro CLI

This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.

## Agenvoy

This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.

## Amp

Merge into ~/.config/amp/settings.json (user) or .amp/settings.json (workspace):

```json
{
  "amp.mcpServers": {
    "llmstxt": {
      "url": "https://agents-mcp-hackathon-llmstxt.hf.space/gradio_api/mcp/sse"
    }
  }
}
```

Then restart the client, or reload its MCP servers, and ask it to list the server's tools to confirm it started.

Tools 2

  • llmstxt_load_doc After getting the registry with the load_registry function, you can use this function to load the documentation you want to use. Returns: The documentation content
  • llmstxt_load_registry This function (load_registry) should always be called first, before using the load_doc function. It will load the registry file and return the content of the registry. Based on that, you will then be able to pick and chose the documentation you want to load. Returns: The content of the registry, that contains the ID, a description and the URL location for each item of the registry, in JSON format

From Hugging Face Spaces. Report a problem