Sociality MCP connects as a remote HTTP MCP server from supported AI tools, CLI clients, and other MCP-compatible environments. The setup flow can vary by client, but the connection model stays the same: connect to the Sociality MCP server, complete OAuth when prompted, and use the client’s MCP interface to start working with Sociality tools, resources, and prompts.

This section focuses on the available setup paths and connection methods, so you can get connected quickly before moving into authentication details, workflow guidance, or reference material.

1. Open ChatGPT > Workspace settings > Apps.
2. Click Create and enter Sociality MCP as the app name.
3. Set MCP Server URL to:

https://api.sociality.io/mcp

4. Set Authentication to OAuth .
5. Check the box for the custom MCP server notice, then click Create.
6. Complete the OAuth flow by signing in to Sociality.io when prompted by ChatGPT, then authorizing the requested permissions.

Setup notes

• After you enter the MCP Server URL, Advanced settings will be enabled. You can leave the detected OAuth settings unchanged unless you need to review them.
• Once setup is complete, the app should appear in your enabled apps list.
• Availability can depend on your ChatGPT plan, workspace settings, and rollout status for custom MCP apps.

1. Open Claude > Settings > Connectors.
2. Click Add custom connector.
3. Enter Sociality MCP as the connector name.
4. Set MCP Server URL to:

https://api.sociality.io/mcp

5. Click Add, then find Sociality MCP in your connectors list and click Connect.
6. Claude will open Sociality.io for OAuth authorization. Sign in if needed, then authorize the requested permissions to connect Sociality.

Setup notes

• Claude may discover the OAuth configuration automatically. Use Advanced settings only if you need to inspect those values before continuing.
• Claude connector availability can depend on your Claude plan, workspace settings, and custom connector support.

Sociality MCP can be used in two setup patterns depending on how your client connects to MCP servers. Some clients connect directly to remote servers over HTTP, while others require a local bridge that proxies requests to the remote endpoint.

Remote HTTP MCP

For environments that support remote HTTP MCP servers, connect to Sociality MCP by registering the remote server URL shown below. Client-specific setup may differ, but you will typically provide the server URL first and complete OAuth during authorization.

{
  "mcpServers": {
    "sociality": {
      "url": "https://api.sociality.io/mcp"
    }
  }
}

STDIO bridge

Use this path for clients built around STDIO-based MCP connections rather than direct remote HTTP access. A bridge such as mcp-remote sits between the client and Sociality MCP, running locally while forwarding traffic to the remote server. This enables remote access without native HTTP MCP support in the client.

{
  "mcpServers": {
    "sociality": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.sociality.io/mcp"]
    }
  }
}

Gemini Enterprise follows a different setup path from consumer AI clients because MCP is configured through enterprise agent-building surfaces such as Agent Designer. Availability can depend on your Google Workspace plan, Gemini Enterprise configuration, admin permissions, and MCP rollout status.

1. Open Gemini Enterprise > Agent Gallery or Agent Designer.
2. Select Create Custom Agent or Add Skill.
3. Choose Connect via MCP and set MCP server URL:

https://api.sociality.io/mcp

4. Complete the Sociality.io OAuth flow if authentication is required.

Sociality MCP can be added to Codex through the CLI as a reusable remote MCP server for future interactions.

codex mcp add --url https://api.sociality.io/mcp sociality

This registers the Sociality endpoint in Codex under the local server name sociality. If authentication is required, Codex will typically prompt you to complete the OAuth flow on first use.

If you are using Claude Code in the terminal, configure Sociality MCP through the CLI rather than the connector UI.

claude mcp add --transport http sociality https://api.sociality.io/mcp

This command registers Sociality as a named MCP server in Claude Code. After registration, use /mcp inside Claude Code to start working with the server. If the session requires authorization, you will need to complete the Sociality.io OAuth flow.

Sociality MCP can be configured in Gemini CLI as a reusable remote MCP server through the local settings file. Start by locating your config file:

~/.gemini/settings.json

Add the following server entry:

{
  "mcpServers": {
    "sociality": {
      "url": "https://api.sociality.io/mcp"
    }
  }
}

Once saved, restart Gemini CLI or run /mcp reload to apply the updated configuration. If authentication is required, Gemini CLI will prompt you to complete the Sociality.io OAuth flow when the server is first used.