MCP.so
Sign In

Gres API MCP Server

@valgresky

Basic information

Category

Developer Tools

License

View license

Transports

stdio

Author

valgresky

About Gres API MCP Server

Gres is a minimalist AI command server for agents and developers. Snap pages, grab sites, source docs, and ask anything. One interface, zero fluff.

Gres API MCP Server config

No standard config provided

This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.

Repository

Gres API MCP Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Gres API?

Gres API is an agentic endpoint layer built with FastAPI, offering modular tools, secure key authentication, and production-ready Docker deployment. It provides endpoints for snapping web pages, crawling sites or sitemaps, listing indexed sources, and querying a vector index via RAG (Retrieval-Augmented Generation).

How to use Gres API?

Set your API key in a .env file as VALGRESKY_API_KEY=sk_valgresky_yourkeyhere. The base URL is https://api.valgresky.com. Use the health check endpoint without authentication (/gres/health). All other endpoints require an X-API-Key header. Invoke endpoints like /gres/snap, /gres/grab, /gres/source, and /gres/ask with appropriate JSON payloads.

Key features of Gres API

  • Health check endpoint without authentication
  • Snap a page with /gres/snap
  • Crawl a site or sitemap with /gres/grab
  • List indexed sources via /gres/source
  • Query vector index (RAG) with /gres/ask
  • API key authentication for all non-health routes

Use cases of Gres API

  • Capture a web page snapshot for archiving or analysis
  • Index an entire website by crawling its sitemap
  • Retrieve metadata about previously indexed sources
  • Ask natural‑language questions against the indexed vector store
  • Deploy as a containerized service with Docker Compose

Frequently asked questions

1

How do I test if the API is running?

Make a GET request to `https://api.valgresky.com/gres/health`. No authentication is required, and it returns `{ "Gres Check": "ok" }`.

2

How do I authenticate my requests?

All main API endpoints require an `X-API-Key` header. Set your key in a `.env` file as `VALGRESKY_API_KEY=sk_valgresky_yourkeyhere` and include it in every request.

3

What endpoints are available?

Four authenticated endpoints: `/gres/snap` (snap a page), `/gres/grab` (crawl a site or sitemap), `/gres/source` (list indexed sources), and `/gres/ask` (query the vector index with RAG). Plus a public health check at `/gres/health`.

4

Can I run Gres API locally with Docker?

Yes. A Docker Compose file is provided that builds the service, exposes port 8051, mounts required directories, and sets environment variables like `OPENAI_API_KEY` and `GRES_EMBEDDINGS_PATH`.

5

What is the MCP integration?

The server includes a shared MCP (Model Context Protocol) instance in `/src/tools/mcp.py`. Tools like `snap` are decorated with `@mcp.tool` and can be invoked as MCP tools, enabling integration with AI agents.

Comments

More Developer Tools MCP servers