Working with Claris MCP - A few Issues...

Questions
1

Hi all,

I have some questions about working with Claris MCP and Claude Desktop.

Q1 : How do I add additional tables to an existing connection in Claris MCP? The documentation says I can add connections in Editing state, but my interface only shows 'generate configuration' with no option to add or edit connections.

Q2 : How do I prevent Claris MCP from returning large container/media fields in update tool responses? The full record data exceeds 1MB and causes Claude errors, but tool descriptions and schema parameters don't control the response size.

Q3 : When using OData vs Data API with Claris MCP, OData returns all fields including large container fields that exceed 1MB, whereas Data API allows managing this through special layouts. What's the recommended approach to handle large container fields in Claris MCP - should I use Data API instead, or is there a way to configure OData to exclude container fields?

Q4 : When setting up Claris MCP connections, how should I choose which tables/relationships to include from a large FileMaker relationship graph if editing the connection later isn't available? What's the best strategy for selecting items initially without excluding tables I might need later?

Q5 : Claris MCP Developer Tools Issue - Simple Summary
Problem: Documented Developer Tools for connection management are not being exposed by the Claris MCP server.

What We Need: Access to connection management tools (specifically update_filemaker_connection) to add tables to existing connections without deleting them.

Current Status:

Context is in Editing state :white_check_mark:
Claude Desktop configured with "Always available" tool access :white_check_mark:
Only 7 tools appear (6 connection-based + 1 developer tool)
Connection-management tools completely absent :cross_mark:
Missing Tools:

get_connections
add_filemaker_connection
update_filemaker_connection
remove_connection
Other connection management tools
Impact: Cannot add tables to existing connections or modify connection configuration as documented.

Question: Is there any way to access the connection management Developer Tools - through Claude Desktop, terminal, API, or any other method?

I am looking thru this now...

2

Q1 - you can't. It's al imitation of the UI, which sucks. It's like a one time deal when you build the MCP, you can't add stuff after the fact. Hopefully they address this as it's a big issue. Best you can do is create a new MCP for the extra tables...

Q2 - I would have thought a tool description forbidding this would be enough, but if not, then you could manage this via the privilege set that the MCP is using to prevent edit access to container fields ?

Q3 - Same - privilege set to restrict this. I'm surprised large containers actually get returned by default. If you're asking for everything from a given record sure, but if you're just asking for specific information , it should be able to just return specific fields from records. I'm surprised it is pulling large container data.

Q4 - Separate file. Make yourself an MCP file that has an external data source to the actual file that contains the tables you want in your MCP. Add just a single TO to the graph in your MCP file for those tables. Ensure both the MCP file and the other data file(s) have the same account with the same privilege set setup with Odata access enabled. This greatly reduces the time required to create the MCP as by default the MCP is going to try and list out every table occurrence in the file which is not ideal. This approach lets you tightly control that, makes setting things up faster too.

Q5 - I don't understand this one sorry.