Skip to content
Minare
EN
Minare

Model Context Protocol

The Minare MCP server

Let your assistant answer “When is Maghrib in Kadıköy tomorrow?” with Minare's engine instead of a guess.

Endpoint
https://minare.app/mcp
Transport
Streamable HTTP, stateless (no sessions), JSON responses
Authentication
Authorization: Bearer mk_… header, or ?key=mk_…

Tools

Setup

Claude Code

claude mcp add --transport http minare https://minare.app/mcp \
  --header "Authorization: Bearer mk_…"

Clients configured with JSON

{
  "mcpServers": {
    "minare": {
      "type": "http",
      "url": "https://minare.app/mcp",
      "headers": {
        "Authorization": "Bearer mk_…"
      }
    }
  }
}

Claude, ChatGPT and other connectors without custom headers

When adding a custom connector, leave authentication at “none” and put the key in the URL. Do not share that URL; you can revoke the key from the dashboard at any time.

https://minare.app/mcp?key=mk_…

Keys come from the developer dashboard: sign in with a passkey and create one. The Trial plan is free and shares its quota with the API.

Get a key

In the browser: WebMCP

The home page and every city page offer WebMCP tools to assistants running inside the browser. They run in the page with the same engine, need no key and use no quota. Without a city they use the one the page shows.

The city search form on every page is a declarative tool too: search_cities.