Where it fits
Marketing analysts who want Google search and ads data in an assistant without exporting spreadsheets.
- Read Search Console data in Claude.
- Review Google Ads performance in Cursor.
- Check AdSense data from any MCP client.
A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.
Skills that pair with MetricPort
These skills cover adjacent tasks, matched by purpose and the work each one describes.
Material on brand voice, visual identity, messaging frameworks, asset management, and keeping a brand consistent. It applies to branded content, tone of voice, marketing assets, brand compliance, and style guides.
Generates brand-kit imagery for high-end brand-guidelines boards, logo systems, identity decks, and visual-world presentations. It is trained for minimalist, cinematic, editorial, dark-tech, luxury, cultural, security, gaming, developer-tool, and consumer-app brand systems, and is optimized for intentional logo concepting, refined composition, sparse typography, strong symbolic meaning, premium mockups, art-directed imagery, and flexible grid layouts.
Creates a product launch, SaaS promo, feature reveal, or app, company, or site marketing video, and can turn a script or brief into a product-focused video. Triggers include a launch video for X, a promo for a site, explaining a SaaS in a minute, a feature reveal for X.com, and turning a script into a 60s promo. It may use a product or marketing URL for brand capture, or work in no-capture mode from a brief or script. It is not for topic explainers with no product or URL (faceless-explainer), or for GitHub PR and code-change videos.
No skills found
Try a different search term or clear the filters.
Install MetricPort
The published npm client runs over stdio and reads METRICPORT_API_KEY or --key mp_.... Claude Desktop, Cursor, Windsurf and VS Code can use the stdio client; clients with remote OAuth can use https://metricport.io/api/mcp instead.
- Create a key
Create an mp_ key at https://metricport.io/app/keys.
export METRICPORT_API_KEY=mp_... - Run the stdio client
Start the npm MCP client with the key in the environment.
npx -y metricport-mcp - Or use the hosted endpoint
Clients that support remote OAuth can connect directly.
claude mcp add --transport http metricport https://metricport.io/api/mcp
Follow the provider's setup steps above, then connect the server in your client. The provider controls the endpoint, required credentials, and permissions.
Endpoint and configuration
The installer uses the server name metricport. If you add the endpoint by hand, keep the same name so the guide and your config match.
Check the connection
After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.
- 1Open the tool list.
Restart the client or start a new session. Confirm that
metricportappears and that the tools match the provider documentation. - 2Run one small request.
Start with: Read Search Console data in Claude. Check the result before you give the server more access.
- 3Check permissions.
Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.
We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. A provider page is linked but was not included in the automated check. Open it before setup.
Common failure modes
These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.
- The sign-in window closes without returning. Allow pop-ups and finish the provider login in the same browser.
- The server connects but its tools are missing. Remove it, add it again, and approve the scopes the provider lists.
- Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Before you connect
- The provider can see the requests and data your agent sends through the server.
- Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
- Use project scope for repository-specific servers; use global scope for personal tools.
- Remove the server and revoke its token when you stop using it.
Check the connection before a real task
These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.
Provider source
Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.
MetricPort repositoryhttps://github.com/MinerSimonDev/metricport-mcp