timesfm
TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.
Unofficial Partner Center REST API knowledge & codegen assistant (scenarios, auth, errors).
Skills that teach the AI this kind of work; they work alongside this one
TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.
Open-source intelligence for the global theater. Track everything from the corporate/private jets of the wealthy, and spy satellites, to seismic events in one unified interface. Hook an AI agent up to have it parse through data and find previously unseen correlations. The knowledge is available to…
scrape data from Google Maps. Extracts data such as the name, address, phone number, website URL, rating, reviews number, latitude and longitude, reviews,email and more for each place
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 6/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 7/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 13/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install Partner Center MCP. Follow https://mcp.popnx.com/i/tunahanaliozturk-partner-center-mcp.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 13, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Partner Center MCP for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "partner-center": { "command": "npx", "args": [ "-y", "partner-center-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Partner Center MCP tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
SettingsDeveloperEdit Config
{
"mcpServers": {
"partner-center": {
"command": "npx",
"args": [
"-y",
"partner-center-mcp"
]
}
}
}Use Partner Center MCP and tell me what you can do for me, then show me one thing✓ If Claude says it is using Partner Center MCP or shows a Partner Center MCP tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Partner Center MCP yet
Partner Center MCP runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Partner Center MCP
Works with Claude Code, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Partner Center MCP for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user partner-center -- npx -y partner-center-mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Partner Center MCP tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user partner-center -- npx -y partner-center-mcpYou should see Partner Center MCP listed as connected
Use Partner Center MCP and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Partner Center MCP or shows a Partner Center MCP tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Partner Center MCP for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "partner-center": { "command": "npx", "args": [ "-y", "partner-center-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Partner Center MCP tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Use Partner Center MCP and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Partner Center MCP or shows a Partner Center MCP tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Partner Center MCP for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "partner-center": { "type": "stdio", "command": "npx", "args": [ "-y", "partner-center-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Partner Center MCP tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Use Partner Center MCP and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Partner Center MCP or shows a Partner Center MCP tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
JSON settings are under “For developers” below
Claude Code
claude mcp add --scope user partner-center -- npx -y partner-center-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"partner-center": {
"command": "npx",
"args": [
"-y",
"partner-center-mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"partner-center": {
"command": "npx",
"args": [
"-y",
"partner-center-mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"partner-center": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"partner-center-mcp"
]
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 20, 2026
The registry name was verified with the GitHub account tunahanaliozturk, which owns the repo
Code last changed 2 months ago
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
No entries on OSV.dev for partner-center-mcp@0.18.0
Checks only this package version, not every dependency · checked Nov 15, 2026
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/tunahanaliozturk-partner-center-mcp)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed 2 months ago, and the latest version (0.18.0) reached the registry 3 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: OpenSEO, Exa, Microsoft Learn MCP, Docs, COTAL actions (cotal.ai)
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Keyword research, site audits, rank tracking and AI visibility for your AI agent.
Official Exa MCP for web search, content fetching, and multi-step research.
Official Microsoft Learn MCP Server – real-time, trusted docs & code samples for AI and LLMs.
Search and read Empryo's documentation. Read-only, no auth, no local access.
cotal.ai actions: product overview, site search, build log, feedback, Cloud waitlist, updates, calls
| This one Partner Center MCP | OpenSEO | Exa | Microsoft Learn MCP | Docs | COTAL actions (cotal.ai) | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | Yes | Yes | Yes | No | No |
| Basic checks | 3/3 | 5/5 | 2/4 | 4/4 | 4/4 | 4/4 |
| License | MIT | MIT | MIT | CC-BY-4.0 | NOASSERTION | Apache-2.0 |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Building against the Partner Center REST API means living in Microsoft Learn. Two hundred odd endpoint pages, an archived .NET SDK that still turns up in search results, and error codes that tell you almost nothing on their own.
This MCP server puts that knowledge next to your agent. Ask how to cancel a subscription and you get the verified method, path, headers, a working code sample, and the constraints the page actually warns about. It holds no credentials and never calls Partner Center. Every answer comes from a bundled knowledge pack, with a cached Microsoft Learn search as the fallback.
Unofficial, community project. Not affiliated with, sponsored, or endorsed by Microsoft.
"Partner Center" and "Microsoft" are trademarks of Microsoft, used here only descriptively.
Microsoft archived the Partner Center .NET SDK (3.4.0) in June 2023 and points partners at the REST APIs instead. Plenty of code still hasn't moved. The retired graph.windows.net audience keeps producing 401 / 900420, and from 2026-04-01 App+User API calls enforce MFA.
So the server does two things. It shows you the current REST and auth patterns, and it explains the errors you hit on the way there.
Your MCP host (Claude Code, Cursor, Copilot, VS Code) talks to the server over MCP, on stdio by default or HTTP if you'd rather. The server reads from a knowledge pack that is zod-validated at load and anchored to official Learn pages. When the pack has no answer it falls back to a cached doc search.
A typical call: the agent picks a tool such as pc_generate_call, the server looks the scenario up in the pack, and back comes the method, path, headers, a ready code sample, and the gotchas, each carrying the docUrl it was verified against.
npx partner-center-mcp
No configuration, API keys, or network access to Partner Center required.
Requires Node.js 20 or newer. (0.9.0 dropped Node 18, which reached end of life in April 2025.)
The server speaks MCP over stdio, so any MCP-capable host works. There's nothing host-specific to install. Use whichever config your host expects:
VS Code (.vscode/mcp.json) and Visual Studio (.mcp.json):
{ "servers": { "partner-center": { "command": "npx", "args": ["-y", "partner-center-mcp"] } } }
GitHub Copilot. Copilot reads the same .vscode/mcp.json (VS Code) / .mcp.json (Visual Studio) shown above; no extra config needed.
Cursor (.cursor/mcp.json) and Windsurf (~/.codeium/windsurf/mcp_config.json):
{ "mcpServers": { "partner-center": { "command": "npx", "args": ["-y", "partner-center-mcp"] } } }
Claude Code:
claude mcp add partner-center -- npx -y partner-center-mcp
Claude Desktop (claude_desktop_config.json), Cline, and Zed use the same mcpServers shape as Cursor above.
Tip: also add the Microsoft Learn MCP server (
https://learn.microsoft.com/api/mcp)
alongside this one for broad documentation search.
Prefer a hosted endpoint over stdio? Run the Streamable HTTP variant:
PORT=3000 npx -p partner-center-mcp partner-center-mcp-http
The endpoint has no authentication of its own, so it binds 127.0.0.1 by default. Request bodies are capped at 1 MiB, and a browser Origin has to be loopback or explicitly allowed, which is what keeps a random web page from driving your local server.
| Variable | Default | What it does |
|---|---|---|
PORT | 3000 | Port to listen on. |
HOST | 127.0.0.1 | Interface to bind. Set 0.0.0.0 only behind a proxy that authenticates. |
ALLOWED_ORIGINS | none | Comma-separated browser origins allowed in addition to loopback. |
MAX_BODY_BYTES | 1048576 | Largest accepted request body. |
| Tool | Purpose |
|---|---|
pc_list_scenarios | List supported REST scenarios, optionally filtered by area. |
pc_get_scenario | Full detail for one scenario: method, path, headers, examples, gotchas. |
pc_generate_call | Emit a current REST call (curl/csharp/typescript/powershell) with auth/retry/pagination helpers. Never the archived SDK. |
pc_validate_request | Lint a REST call (method, URL, headers, auth) against the known scenarios. |
pc_plan_purchase | The ordered New Commerce purchase workflow: product → SKU availability → cart → checkout → subscriptions. |
pc_migrate_from_sdk | Translate archived .NET SDK code into the equivalent REST scenario(s). |
pc_auth_guidance | Current auth guidance for app-only / app+user, per national cloud, with GDAP + MFA notes. |
pc_check_auth | Lint an auth/client snippet for retired patterns (graph.windows.net, ADAL, archived SDK, AzureAD PS). |
pc_build_request | Build a ready-to-send request: fills path placeholders, generates MS-RequestId/MS-CorrelationId, and a body skeleton from the scenario's fields. |
pc_explain_lifecycle | What you can do to a subscription in its current state: legal operations, the field each precondition reads, and the errors a failed precondition returns. |
pc_plan_subscription_change | Ordered call sequence for one lifecycle change: seats up/down, upgrade, cancel, renewal changes, suspend, reactivate, migrate, transfer. |
pc_plan_order_lifecycle | Ordered call sequence from cart to *provisioned* subscriptions, with the cancellation and add-on branches. |
pc_plan_transfer | Ordered billing-ownership transfer workflow (create → poll → verify). |
pc_plan_gdap_onboarding | Ordered GDAP onboarding workflow (create → approve → verify) over Microsoft Graph. |
pc_plan_csp_onboarding | Ordered CSP customer onboarding (account linking): invite → verify relationship → confirm agreement → transact. |
pc_plan_user_onboarding | Ordered user onboarding: create user → assign licenses → grant roles → verify. |
pc_plan_user_offboarding | Ordered user offboarding: remove licenses → strip roles → delete user (30-day restore window). |
pc_plan_reconciliation | Ordered reconciliation workflow (invoice → billed/unbilled line items → statement). |
pc_lookup_error | Decode an error code: causes, remediation, and the scenarios it commonly hits. |
pc_decode_error | Paste a raw error response → decoded code, likely scenarios, and the correlation id for support. |
pc_diagnose | Map a symptom to likely causes, fixes, and relevant scenarios. |
pc_get_enums | Look up enum values (billingCycle, termDuration, targetView, transitionType, status, …). |
pc_get_resource | Field dictionary for resources (Customer, Subscription, Order, Invoice, migration schedules, …). |
pc_whats_new | Deprecations & deadlines (MFA enforcement, graph.windows.net, v1→v2 reconciliation, …). |
pc_plan_prerequisites | For any scenario, the ordered calls that produce the ids its path needs, and the parameters you supply yourself. |
pc_diff_pack | What changed between pack releases: scenarios added, removed, or whose route, auth, fields or constraints moved. |
pc_search_docs | Fetch live Microsoft Learn excerpts. The fallback when the curated pack has no answer. |
pc_get_reference | Base URLs, headers, versioning, sandbox, rate limits, national-cloud differences. |
Every tool carries the metadata a calling agent needs: a title, a description that says when to use it *and* which sibling to prefer instead, a description on every input parameter, a declared outputSchema, and MCP behaviour annotations. All 28 are readOnlyHint: true and destructiveHint: false, because the server holds no credentials and calls no Partner Center endpoint. It only reads the bundled pack. Three tools break idempotentHint or openWorldHint: pc_search_docs and pc_get_scenario with enrich: true both reach Microsoft Learn, and pc_build_request mints a fresh MS-RequestId on every call.
Responses share one envelope. { ok, data } on success, { ok: false, error, suggestions? } on failure, returned as structuredContent and validated against each tool's outputSchema by the MCP SDK.
Scenarios cover:
Every scenario carries the docUrl it was verified against and the date it was last checked, and 185 of them ship the response example their page publishes, so field names and nesting can be read off rather than guessed at. National clouds covered: commercial, 21Vianet (China), and US Gov.
Lifecycle changes come with their *preconditions*, not just their endpoints. pc_explain_lifecycle returns the state machine: which operation is legal from which state, the field to read off the live subscription first (cancellationAllowedUntilDate, autoRenewEnabled, suspensionReasons), and the error you get when the precondition fails.
The pack is also browsable as MCP resources (pc://scenarios, pc://errors, pc://auth, pc://reference, pc://sdk-map, pc://enums, pc://deprecations, pc://resources, pc://lifecycle, pc://examples, pc://history, pc://scenario/{id}) and three prompts (migrate-sdk, diagnose-issue, plan-purchase) for hosts that surface them.
Alongside the scenarios it ships enum values, a resource field dictionary, and a deprecations and deadlines timeline. npm run export turns the whole pack into an OpenAPI 3.0 spec and a Postman collection.
Decode an error you hit in production:
// pc_lookup_error { "code": "900420" }
{ "httpStatus": 401, "errorCode": "900420", "description": "The audience in the token is invalid and is no longer supported in Partner Center API.", "causes": ["Token requested with the retired graph.windows.net audience"], "remediation": "Request the token with resource https://api.partnercenter.microsoft.com ...", "docUrl": "https://learn.microsoft.com/partner-center/developer/deprecate-azure-active-directory-graph-token" }
Lint old auth/client code before you ship it:
// pc_check_auth { "code": "new AuthenticationContext(); get(\"https://graph.windows.net\"); partner.Customers..." }
{ "findings": [ { "severity": "error", "message": "Uses the retired graph.windows.net audience; Partner Center returns 401 / 900420.", "fix": "Request the token with resource https://api.partnercenter.microsoft.com." }, { "severity": "warning", "message": "App