semantic_queryLABSCO SUMMARY
Find the endpoint without reading the documentation site.
It answers the question you actually have - what call does this - with the parameters and auth attached, and will go and read an unfamiliar provider's docs to answer rather than returning nothing.
What it is
A search layer over Semantic API's hosted index of APIs. You describe the capability you need - "send an email with Gmail", "convert currencies in real time" - and it returns endpoint details, parameters, authentication and code snippets, discovering the API first if the index has not seen it.
What you get
- An API capability found from a plain-English description, with endpoint, parameters, auth and a snippet
- New APIs discovered on the fly when the index does not already hold one, rather than an empty result
- A named provider explored in depth against what you actually want to do with it - "stripe", for "process a refund"
- Any API analysed from its documentation URL, turning a docs page into a provider configuration
Requirements
A Semantic API account and SEMANTIC_API_KEY. Install with pip or run it with uvx. The API base URL can be overridden in the environment if you need to point at a different one.
Setup effort
One command plus a key — pip install semanticapi-mcp, then supply credentials
USE CASES
01
Finding a service that does the thing you need
Describe the capability in words and get the endpoint that provides it, with parameters and auth already filled in.
02
Working out what a provider you already use can do
Name the provider and what you want done with it, and get the relevant part of its API rather than its whole surface.
03
Getting to grips with an API from its docs page
Hand over the documentation URL and get a usable provider configuration out of it.
04
Writing the integration in one pass
Take the snippet that comes back with the endpoint, so the first version of the call is not assembled from memory.
3 tools
Listed in project docs. Your client may show a different list.
semantic_discoversemantic_discover_urlBEFORE YOU INSTALL
What to know first
Tools you get
3 tools named in the project's documentation.
Requires
- uvx on PATH
- SEMANTIC_API_KEY in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
pip install semanticapi-mcpMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"semanticapi": {
"command": "uvx",
"args": [
"semanticapi-mcp"
],
"env": {
"SEMANTIC_API_KEY": "<YOUR_SEMANTIC_API_KEY>"
}
}
}
}
