datavessel
io.datavesselPublished by datavessel.ioOfficial publisherv0.1.0Updated Oct 24, 2026
200+ read/write tools for GA4, Search Console, Google Ads, Shopify, WooCommerce, Shopware & more.
Overview
Remote MCP server giving an assistant 200+ read/write tools across GA4, Search Console, Google Ads, Shopify, WooCommerce and Shopware.
- What you can do
- Connect to analytics and advertising accounts such as GA4, Search Console and Google Ads to read and write data.
- Work with ecommerce stores on Shopify, WooCommerce and Shopware through the same tool set.
- Cover additional connected platforms beyond those named, since the provider lists 200+ tools in total.
- Both read and write operations are offered, so an assistant can change data as well as report on it.
- When to use it
- Useful when an assistant needs to pull marketing, analytics or store data from several platforms in one place, or to make changes in those accounts rather than only read them. Suited to teams running Google advertising and ecommerce stores who want a single connector instead of separate integrations.
- Requirements
- A remote MCP endpoint at mcp.datavessel.io over streamable HTTP. OAuth authentication is required, so the user must sign in and authorize access to the connected platforms. No environment variables or headers are declared.
Installation
In SourceWeft
- Open datavessel in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- 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/io.datavessel%2Fmcp/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. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"datavessel": {
"type": "http",
"url": "https://mcp.datavessel.io/mcp"
}
}
}Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
67% 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.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.