What does Token Forge Cloud do?

Token Forge Cloud provides managed APIs for Qwen, DeepSeek, GLM, and Seedance, with additional video and speech models for teams building production AI products. Proven workloads can also move into a Neo Cloud marketplace product path.

Who is Token Forge Cloud built for?

It is built for product and enterprise teams that need reliable language, reasoning, coding, agent, and video model access without operating every provider stack themselves.

Can teams start with APIs before buying through Neo Cloud?

Yes. Teams can begin with managed API access for Qwen, DeepSeek, GLM, Seedance, and additional media models, then move predictable production traffic into a Neo Cloud marketplace product path.

Which AI workflows does Token Forge Cloud support?

Token Forge Cloud supports assistants, reasoning, coding, agents, text-to-video, image-to-video, asynchronous jobs, model routing, and speech generation.

How does Token Forge Cloud handle security and data control?

Token Forge Cloud supports role policies for who can call which models and workflows, controlled access for prompts and application data, and audit-ready request, generation, and routing telemetry.

Remove an MCP Server from Claude Code

To remove one MCP server without uninstalling Claude Code, first check its exact name and scope with claude mcp get <name>, then run claude mcp remove <name>. If the same name exists at multiple scopes, specify the one to remove with --scope. The scopes differ: local is private to you and active only in the current project; user applies across your projects; and project is for sharing with teammates. (code.claude.com)

Remove the intended server

Open a terminal in the project you mean to check, then list configured servers:
```
claude mcp list
```
Use the configured server name—not its URL or package name—to inspect its scope:
```
claude mcp get <server-name>
```
Claude Code’s quickstart says this command shows which scope holds a server’s definition. If you are targeting a project-specific registration, make sure you are in that project’s directory; local-scope registrations are active only in the current project. (code.claude.com)
Remove the registration by name:
```
claude mcp remove <server-name>
```
If Claude Code reports that the name exists at more than one scope, choose the intended copy explicitly. For example:
```
claude mcp remove <server-name> --scope local
```
The official quickstart documents --scope for selecting which copy to remove when a name exists in multiple scopes. (code.claude.com)
Run claude mcp list again. If the name still appears, use claude mcp get <server-name> to check which scope still has a definition; a remaining same-named entry does not by itself show that the copy you targeted was not removed. The official quickstart documents claude mcp get as the way to see the scope holding a definition. (code.claude.com)

A community-authored Qiita example—not an official success-output guarantee—shows claude mcp remove aws-knowledge-mcp returning “Removed MCP server” and reporting a modified .claude.json file. Treat that as an example of output, not proof that every scope or same-named registration was removed. (code.claude.com)

If the server is still listed

Check the scope with claude mcp get <server-name>. If the name is configured in more than one scope, Claude Code documents that removal can report the multiple-scope case; use --scope to select the intended copy. Remove another copy only if you mean to, then list again. The claude mcp list output alone should not be treated as identifying the scope. (code.claude.com)

Avoid deleting .mcp.json, .claude.json, or other configuration files as a shortcut for removing one server. A third-party article lists those files in a complete Claude Code uninstall procedure, which is a different task from selective MCP removal. (code.claude.com)

If you use OAuth with the MCP server and also want to revoke its authorization, Claude Code’s MCP reference says to run claude mcp logout <name> before removing it; removal alone does not revoke tokens at the authorization server. (code.claude.com)

Does removing MCP change a production model API?

The material reviewed here does not establish whether removing a particular MCP server changes a production model API endpoint, key, or billing arrangement. Do not treat claude mcp remove as a way to change or revoke model API settings; check those settings in the system that manages them. (code.claude.com)

Removing an MCP server is not the same as uninstalling Claude Code. Identify the server and scope, remove the intended registration, and check the resulting list; do not delete broad configuration files or uninstall the CLI.

Sources

Connect to MCP servers — Claude Code Docs

Connect Claude Code to tools via MCP — Claude Code Docs

Claude CodeのMCPサーバ削除コマンドメモ

How to Completely Remove Claude Code — CometAPI