Point MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| POINT_API_KEY | Yes | Your Point API key (get one at https://pinchpoint.dev/point/keys) | |
| POINT_API_URL | No | API base URL (for self-hosted or local dev) | https://point-api.pinchpoint.dev |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchA | Search Point's verified knowledge base using hybrid search (BM25 + vector). Returns ranked results with relevance scores, text excerpts, and citations. Each result includes a pre-formatted citation you can use directly. |
| get_document_tocA | Get a lightweight table of contents for a document (~50 tokens). Use this to understand document structure before loading specific sections. Returns chunk IDs that you can pass to get_sections. |
| get_sectionsA | Load specific document sections by their chunk IDs (max 50 per request). Use after search or get_document_toc to retrieve full text of specific passages. Each section includes its text, heading path, word count, and citation. |
| list_collectionsA | Browse or search available knowledge collections. Without a query, lists all collections with document counts. With a query, performs semantic search to find relevant collections. |
| get_document_fullA | Get the full markdown content of a document. WARNING: This can be large (thousands of tokens). Prefer get_document_toc + get_sections for targeted retrieval. Use this only when you need the complete text. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a distinct purpose: full document retrieval, table of contents, section loading, collection listing, and search. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern (get_document_full, get_document_toc, get_sections, list_collections, search). Even 'search' fits as a verb with an implied object.
With 5 tools, the server is well-scoped for knowledge base retrieval. It is neither too sparse nor too heavy.
The tool set covers all necessary operations for a read-only knowledge base: browsing collections, searching, getting document structure, and retrieving full or partial content. No gaps for its stated purpose.