gurixandClaude
82a2a46a8e
Add comprehensive proposal to update the TypeScript MCP server to support organization members. The GraphQL backend was updated in the feat/organization-member-support branch to add memberType and companyName fields, but the MCP server tools still assume all members are individuals. Proposal includes: - Detailed design for updating tool definitions and GraphQL queries - Member formatting logic to distinguish individuals from organizations - Comprehensive spec deltas with 22 scenarios covering all use cases - 11 implementation tasks All changes are contained in a single file: src/mcp_server.ts 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
16 lines
1.1 KiB
Markdown
16 lines
1.1 KiB
Markdown
# Tasks: Update MCP Server for Organization Members
|
|
|
|
- [ ] Update `create_member` tool definition with memberType and companyName fields <!-- id: 0 -->
|
|
- [ ] Update `update_member` tool definition with memberType and companyName fields <!-- id: 1 -->
|
|
- [ ] Add memberType and companyName to listMembers GraphQL query <!-- id: 2 -->
|
|
- [ ] Add memberType and companyName to getMember GraphQL query <!-- id: 3 -->
|
|
- [ ] Add memberType and companyName to createMember mutation response <!-- id: 4 -->
|
|
- [ ] Add memberType and companyName to updateMember mutation response <!-- id: 5 -->
|
|
- [ ] Update formatMember function to distinguish between individual and organization members <!-- id: 6 -->
|
|
- [ ] Test individual member creation (verify existing behavior) <!-- id: 7 -->
|
|
- [ ] Test organization member creation (verify new behavior) <!-- id: 8 -->
|
|
- [ ] Test member listing with mixed member types (verify formatting) <!-- id: 9 -->
|
|
- [ ] Verify GraphQL schema introspection includes MemberType enum <!-- id: 10 -->
|
|
|
|
**Note**: All changes are in a single file: `src/mcp_server.ts`
|