Alternate Programmatic Access

Prerequisites

System requirements

• Poggio workspace with administrator privileges

• MCP server entitlements enabled for your workspace

• External MCP clients (LLM chat applications, custom applications, custom agents, or any other software systems with support for leveraging MCP server capabilities.)

• Network connectivity between clients and Poggio's MCP server

Access requirements

• Poggio workspace administrator role

• Ability to configure external MCP clients

• Working knowledge of client-side MCP configuration and network transport

Step 1: Access MCP server settings in Poggio

1. Navigate to your Poggio workspace

2. Click on "Settings" in the left sidebar

3. Select "MCP Server" from the settings menu

Note: If you don't see the MCP Server option, this feature may not be enabled for your workspace. Contact your Poggio administrator or support.

Step 2: Locate the Poggio MCP server URL

At the top of the MCP Server settings page, you'll find the external Poggio MCP server URL. Use the copy button to copy it exactly from the UI.

This URL will be used to configure external MCP clients to connect to your Poggio workspace.

Note: The connection URL does not include a workspace identifier; workspace scoping is implicitly enforced via the generated API token

Step 3: Generate an API token for authentication with the Poggio MCP server

Create your first token

1. Click "Generate token" to create a new API token

2. The Create API Token dialog will open

Configure token details

In the Create API Token dialog, provide a descriptive name for the token (e.g., "ACME Slack agent ", "RevOps Control Panel", etc.)

Secure token storage

After creating a token:

1. Copy the token immediately - it will only be shown once

2. Store the token securely in your password manager or secure documentation

3. The token will appear in your token list with partial masking for security

Step 4: Configure your external MCP client

The configuration steps vary by client type:

1. Open your client application and locate the MCP server settings interface

2. Add a new MCP server using the URL copied from Poggio settings

3. Provide the API token as a Bearer token if your client supports it, or in the client’s designated token field

4. Save the configuration. You may need to restart the client so it can discover tools from the Poggio MCP

Note: Different MCP clients have different configuration formats. Refer to your client’s documentation for how to set a remote HTTP MCP server URL and Bearer token. The Poggio server uses standard HTTPS MCP transport and requires Authorization: Bearer <secure-token> to be present in the request headers.

Example: Custom application integration

For custom applications using MCP client libraries (Python example):

poggio_client_example.py

from mcp import ClientSession
from mcp.client.streamable_http import streamablehttp_client

url = "https://mcp.poggio.io/mcp"  # or copy from settings
headers = {"Authorization": "Bearer YOUR_API_TOKEN_HERE"}

async with streamablehttp_client(url=url, headers=headers) as (r, w, _):
    async with ClientSession(read_stream=r, write_stream=w) as session:
        await session.initialize()
        tools = await session.list_tools()
        print([t.name for t in tools.tools])

Step 5: Test the Connection

Verify client connection

1. Restart your MCP client application

2. Check that Poggio appears in the list of connected servers

3. Verify available tools and capabilities are discovered

Test Poggio capabilities

Try these example interactions to verify the connection:

• "What Poggio tools do you have access to?"

• "List the available info from Poggio for the <example.com> account"

The MCP inspector is frequently useful at this stage, providing a friendly UI for connecting to remote MCP servers, exploring their capabilities, and invoking tools directly. To launch this development tool locally, run the following (requires Node v22.x+):

$ npx @modelcontextprotocol/inspector \
  --transport=http \
  --server-url=https://mcp.poggio.io/mcp

Paste your MCP auth token directly into the Bearer token input box, then click "Connect"

Step 6: Manage API tokens

Monitor token usage

1. Review the token list in your MCP Server settings

2. Check last used dates and activity patterns

Update token settings

• Edit: Click the pencil icon to modify token name or expiration

• Revoke: Click the trash icon to immediately revoke access

Token security best practices

• Use descriptive names to track token purpose

• Regularly audit and rotate tokens

• Immediately revoke tokens that are no longer needed