mcp-saas-connector
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STRIPE_API_KEY | No | Stripe API key (restricted key with read permissions). Enables Stripe tools. | |
| HUBSPOT_ACCESS_TOKEN | No | HubSpot private app token scoped to contacts and deals. Enables HubSpot tools. | |
| CONNECTOR_ALLOW_WRITES | No | Set to 'true' to register write tools (hubspot_create_contact, hubspot_create_note, sheets_append_row). Anything else keeps them off. | false |
| GOOGLE_SERVICE_ACCOUNT_JSON | No | Google service account JSON (inline or file path). Enables Google Sheets tools. Share target sheets with the service account email. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| connector_statusA | Report which providers are enabled, whether write tools are registered, and how to enable more. |
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 1 tool
Only one tool exists, so there is no possibility of confusion between tools.
With a single tool, naming is trivially consistent.
A 'saas-connector' server with only one status tool is too thin; expected multiple tools for CRUD or provider management.
Lacks any operational tools to actually interact with SaaS providers; severely incomplete for the stated purpose.