Devotd Github
NewModel Context Protocol

voltagent/official-mcp-servers — Datacircle server added to README

A new entry, Datacircle — a server for the GTM API — was added to the README of the official MCP server listing repository voltagent/official-mcp-servers on November 2, 2026.

Repositoryvoltagent/official-mcp-servers ↗

A new entry, Datacircle — a server for the GTM API — was added to the README of the official MCP server listing repository voltagent/official-mcp-servers on November 2, 2026.

GitHub description: A curated directory of 390+ official MCP servers from the companies behind the products. No unofficial forks, no abandoned projects.

stars
★ 360
Forks
71
License
MIT
Read original source ↗View on GitHub ↗

One new entry was added on November 2, 2026 to the index repository voltagent/official-mcp-servers, which collects more than 390 official MCP servers. Commit 9183df9 is the merge of PR #73 submitted by waynehamadi, and the change consists of a single added line introducing the Datacircle server in README.md. The change affects 1 file, with 1 insertion and 0 deletions.

This repository is not a place where code is stored, but a list. The repository description states that it covers only the official MCP servers made directly by the companies behind the products, and makes clear that it does not cover unofficial forks or abandoned projects. The README describes the purpose of the list as follows: MCP servers can read users' data and act on their behalf, so who made them matters. In the block where the new line was inserted, entries for BestPrice, npmscan, and Keenable were already lined up. The newly listed Datacircle is introduced in the README as a server that finds the GTM API, and its link points not to a GitHub repository but to the datacircle.dev/docs/mcp documentation.

However, the only thing the commit confirms is that one line. The source code repository, license, maintenance status, and list of tools actually exposed by the Datacircle server were not presented alongside it. Unlike the other entries in the list, which lead to repository addresses, this entry points only to the parent service's documentation, so to judge what data the server has access to, one has to open the documentation directly. Only the composition of the index changed, by as much as one added line, and it is hard to consider the server's behavior confirmed on the basis of this commit alone.