PILLAR GTM OS

com.pillargtmPublished by pillargtm.comOfficial publisherv1.0.0Updated Oct 24, 2026

AI-native GTM OS for B2B SaaS — account health, pipeline, renewals, territories, and benchmarks.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

A remote MCP endpoint for PILLAR GTM OS, a B2B SaaS go-to-market platform covering account health, pipeline, renewals, territories and benchmarks.

What you can do
Connect an assistant to a B2B SaaS go-to-market workspace covering account health, pipeline, renewals, territories and benchmarks. The manifest lists no individual tools, so the exact actions available are not documented here. Access is authenticated with a PILLAR API key sent as a bearer token.
When to use it
Useful when you want an AI assistant to work with go-to-market data for a B2B SaaS business — accounts, pipeline, renewals, territories or benchmarks — through the PILLAR platform rather than a local tool.
Requirements
A remote streamable HTTP endpoint at app.pillargtm.com. A PILLAR account and an API key generated in Settings > Integrations, sent in the Authorization header as a bearer token (format Bearer pk_live_...). Network access is required.
Before you install
The API key is a live credential (pk_live_ prefix) sent in the Authorization header; treat it as a secret and avoid exposing it in logs or shared configurations. The manifest does not document which tools exist or whether they can change data, so confirm read versus write behavior before relying on it.

Installation

In SourceWeft

  1. Open PILLAR GTM OS in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.pillargtm%2Fgtm-os/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "pillar-gtm-os": {
      "type": "http",
      "url": "https://app.pillargtm.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

This repository has no README.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.