
Ascend GTM Gateway
net.ascendgtmPublished by ascendgtm.netv5.3.0Updated Oct 24, 2026
34-tool GTM gateway: CRMs, ad platforms, analytics, Google Workspace, AWS, and LLM orchestration.
Overview
A remote gateway exposing 34 tools that connect an assistant to CRMs, ad platforms, analytics, Google Workspace, AWS, and LLM orchestration.
- What you can do
- Ascend GTM Gateway is a remote MCP endpoint that presents a single 34-tool surface spanning several business systems. According to its description, those tools cover CRM platforms, advertising platforms, analytics, Google Workspace, AWS, and LLM orchestration. No individual tool names, parameters, or return formats are published, so the exact operations available are not documented in the supplied material.
- When to use it
- Consider it when an assistant needs to work across go-to-market systems — customer records, ad campaigns, reporting, workspace documents, and cloud resources — through one connection instead of several separate servers. It is less suitable if you only need one of those systems, or if you need documented tool behavior before connecting.
- Requirements
- It runs as a remote streamable HTTP endpoint at the provider's hosted address, so no local runtime or package install is needed. The manifest declares no authentication, no environment variables, and no headers, but the underlying services it reaches (CRM, ads, analytics, Google Workspace, AWS) would normally require their own credentials.
Installation
In SourceWeft
- Open Ascend GTM Gateway in the dashboard and add it to a workspace.
- 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/net.ascendgtm%2Fgateway/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.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"ascend-gtm-gateway": {
"type": "http",
"url": "https://ascend-gateway-v5.ascendgtm.workers.dev/mcp"
}
}
}README
This repository has no README.
Tools
0Version history
1- v5.3.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 listedRequired15 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.