Schema | portal-api

portal-api

Describes the environment variables required to run the server.

Name	Required	Description	Default
`PORTAL_ENV`	Yes	Environment: sandbox or production
`PORTAL_APP_ID`	Yes	API application key
`PORTAL_BASE_URL`	Yes	Base URL for Portal API
`PORTAL_SECRET_KEY`	Yes	Secret key for HMAC signing
`PORTAL_USER_API_KEY`	Yes	Base64-encoded User API Key from credential exchange, typically 44 characters
`PORTAL_WRITE_ENABLED`	No	Enable write operations (not yet supported)	false

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.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": true }

Functions exposed to the LLM to take actions

Name	Description
test_connectionA	Confirm that the configured Portal.io API credentials work. This is read-only and returns only proposal metadata.
list_proposalsB	List or search Portal.io proposals. Read-only.
get_proposalA	Get complete details for one Portal.io proposal. Read-only.
list_usersA	List active users in the Portal.io account. Use this to find salesperson IDs. Read-only.
search_contactsB	Search or list Portal.io contacts. Read-only.
search_catalogB	Search the Portal.io catalog. Catalog API access must be enabled for the account. Read-only.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AWfusion/portal-api-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server