Circle MCP Server

Overview Schema Source Related Servers Discussions Admin

Update Connect settings

update_connect_settings

Destructive

Updates community Connect settings, including connections, messaging, and member directory options. Requires confirm=true to apply a user-requested change.

Instructions

Update Connect settings. Changes community state and requires confirm=true for the user-requested action.

Input Schema

TableJSON Schema

Name	Required	Description
`account`	No	Named private Circle account; selects credentials, not a remote community ID.
`confirm`	No	Set true only when the user asked for exactly this action.
`connect`	No
`payload`	No	Complete JSON request body instead of body flags. Supports nested Tiptap, maps and nullable values.
`messaging`	No
`payload_file`	No	Regular local JSON body file, at most 5 MB. Cannot be mixed with body flags or payload.
`member_directory`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed20 schema fields changedv3.0.1Oct 7, 2026

addedInput schema / $defs

Added value: +{
+  "connect": {
+    "properties": {
+      "enabled": {
+        "description": "Whether the Connect feature is enabled for the community",
+        "type": "boolean"
+      },
+      "exclude_admins_from_recommendations": {
+        "description": "Whether admins are excluded from connection recommendations",
+        "type": "boolean"
+      },
+      "exclude_moderators_from_recommendations": {
+        "description": "Whether moderators are excluded from connection recommendations",
+        "type": "boolean"
+      },
+      "recommendations": {
+        "description": "Whether member-to-member connection recommendations are enabled. Only effective when connect.enabled is true.",
+        "type": "boolean"
+      }
+    },
+    "type": "object"
+  },
+  "member_directory": {
+    "properties": {
+      "public": {
+        "description": "Whether the member directory is publicly visible",
+        "type": "boolean"
+      },
+      "sort": {
+        "description": "Default sort order for the member directory",
+        "enum": [
+          "alphabetical",
+          "oldest",
+          "latest"
+        ],
+        "type": "string"
+      },
+      "view": {
+        "description": "Default view layout for the member directory",
+        "enum": [
+          "list",
+          "cards"
+        ],
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "messaging": {
+    "properties": {
+      "enabled": {
+        "description": "Whether messaging is enabled for the community (master toggle)",
+        "type": "boolean"
+      },
+      "group_messaging_enabled": {
+        "description": "Whether members can create group chats",
+        "type": "boolean"
+      },
+      "member_to_member_messaging_enabled": {
+        "description": "Whether members can direct message one another",
+        "type": "boolean"
+      },
+      "require_connection_before_messaging": {
+        "description": "Whether members must be connected before they can message each other",
+        "type": "boolean"
+      },
+      "voice_messages_enabled": {
+        "description": "Whether voice messages are enabled in chats",
+        "type": "boolean"
+      }
+    },
+    "type": "object"
+  }
+}

changedInput schema / properties / confirm / description

Previous value: -"Must be true for the specific user-requested write."New value: +"Set true only when the user asked for exactly this action."

addedInput schema / properties / connect / $ref
```
Added value: +"#/$defs/connect"
```

removedInput schema / properties / connect / properties

Removed value: -{
-  "enabled": {
-    "description": "Whether the Connect feature is enabled for the community",
-    "type": "boolean"
-  },
-  "exclude_admins_from_recommendations": {
-    "description": "Whether admins are excluded from connection recommendations",
-    "type": "boolean"
-  },
-  "exclude_moderators_from_recommendations": {
-    "description": "Whether moderators are excluded from connection recommendations",
-    "type": "boolean"
-  },
-  "recommendations": {
-    "description": "Whether member-to-member connection recommendations are enabled. Only effective when connect.enabled is true.",
-    "type": "boolean"
-  }
-}

removedInput schema / properties / connect / type
```
Removed value: -"object"
```
addedInput schema / properties / member_directory / $ref
```
Added value: +"#/$defs/member_directory"
```

removedInput schema / properties / member_directory / properties

Removed value: -{
-  "public": {
-    "description": "Whether the member directory is publicly visible",
-    "type": "boolean"
-  },
-  "sort": {
-    "description": "Default sort order for the member directory",
-    "enum": [
-      "alphabetical",
-      "oldest",
-      "latest"
-    ],
-    "type": "string"
-  },
-  "view": {
-    "description": "Default view layout for the member directory",
-    "enum": [
-      "list",
-      "cards"
-    ],
-    "type": "string"
-  }
-}

removedInput schema / properties / member_directory / type
```
Removed value: -"object"
```
addedInput schema / properties / messaging / $ref
```
Added value: +"#/$defs/messaging"
```

removedInput schema / properties / messaging / properties

Removed value: -{
-  "enabled": {
-    "description": "Whether messaging is enabled for the community (master toggle)",
-    "type": "boolean"
-  },
-  "group_messaging_enabled": {
-    "description": "Whether members can create group chats",
-    "type": "boolean"
-  },
-  "member_to_member_messaging_enabled": {
-    "description": "Whether members can direct message one another",
-    "type": "boolean"
-  },
-  "require_connection_before_messaging": {
-    "description": "Whether members must be connected before they can message each other",
-    "type": "boolean"
-  },
-  "voice_messages_enabled": {
-    "description": "Whether voice messages are enabled in chats",
-    "type": "boolean"
-  }
-}

removedInput schema / properties / messaging / type
```
Removed value: -"object"
```
addedInput schema / properties / payload / properties / connect / $ref
```
Added value: +"#/$defs/connect"
```

removedInput schema / properties / payload / properties / connect / properties

Removed value: -{
-  "enabled": {
-    "description": "Whether the Connect feature is enabled for the community",
-    "type": "boolean"
-  },
-  "exclude_admins_from_recommendations": {
-    "description": "Whether admins are excluded from connection recommendations",
-    "type": "boolean"
-  },
-  "exclude_moderators_from_recommendations": {
-    "description": "Whether moderators are excluded from connection recommendations",
-    "type": "boolean"
-  },
-  "recommendations": {
-    "description": "Whether member-to-member connection recommendations are enabled. Only effective when connect.enabled is true.",
-    "type": "boolean"
-  }
-}

removedInput schema / properties / payload / properties / connect / type
```
Removed value: -"object"
```
addedInput schema / properties / payload / properties / member_directory / $ref
```
Added value: +"#/$defs/member_directory"
```

removedInput schema / properties / payload / properties / member_directory / properties

Removed value: -{
-  "public": {
-    "description": "Whether the member directory is publicly visible",
-    "type": "boolean"
-  },
-  "sort": {
-    "description": "Default sort order for the member directory",
-    "enum": [
-      "alphabetical",
-      "oldest",
-      "latest"
-    ],
-    "type": "string"
-  },
-  "view": {
-    "description": "Default view layout for the member directory",
-    "enum": [
-      "list",
-      "cards"
-    ],
-    "type": "string"
-  }
-}

removedInput schema / properties / payload / properties / member_directory / type
```
Removed value: -"object"
```
addedInput schema / properties / payload / properties / messaging / $ref
```
Added value: +"#/$defs/messaging"
```

removedInput schema / properties / payload / properties / messaging / properties

Removed value: -{
-  "enabled": {
-    "description": "Whether messaging is enabled for the community (master toggle)",
-    "type": "boolean"
-  },
-  "group_messaging_enabled": {
-    "description": "Whether members can create group chats",
-    "type": "boolean"
-  },
-  "member_to_member_messaging_enabled": {
-    "description": "Whether members can direct message one another",
-    "type": "boolean"
-  },
-  "require_connection_before_messaging": {
-    "description": "Whether members must be connected before they can message each other",
-    "type": "boolean"
-  },
-  "voice_messages_enabled": {
-    "description": "Whether voice messages are enabled in chats",
-    "type": "boolean"
-  }
-}

removedInput schema / properties / payload / properties / messaging / type
```
Removed value: -"object"
```

First observedv2.0.0Oct 2, 2026

TDQS

B3.3/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the risk profile is covered by structured data. The description's added value is the confirm gate tying the mutation to an explicit user request, but it says nothing about partial-merge behavior, what happens to omitted settings, or permission requirements for a destructive multi-section update.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, mutation scope front-loaded, no filler. It is efficient, though the brevity is partly a symptom of under-specification rather than disciplined trimming.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, non-idempotent tool with 7 parameters, deep nested objects, three mutually exclusive body-passing mechanisms and no output schema, two sentences are far too thin. The agent must go entirely to the schema to learn how to construct a valid call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 57% with 7 parameters, so the description should compensate more than it does. It only restates the confirm parameter, which the schema already documents verbatim in spirit, and says nothing about the payload vs. body-flags vs. payload_file exclusivity or the nested connect/messaging/member_directory groups.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Update Connect settings') and adds that it changes community state. It does not differentiate itself from the sibling get_connect_settings, so the agent gets the purpose but not the contrast.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives one concrete precondition ('requires confirm=true for the user-requested action'), which is genuine conditional guidance. However it never says when to choose this over get_connect_settings or other update_* configuration tools, leaving the selection decision implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Update Connect settings

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools