Hidesc MCP connector

Connect Hidesc to Claude

Bring your Hidesc work into Claude. Connect your account through the Model Context Protocol (MCP), then ask Claude to use the information and actions available to you.

Remote MCP server URL

https://mcp.hidesc.com/mcp

Before you connect

  • A Claude account with access to custom remote connectors. Your organization may need to enable this feature.
  • An existing Hidesc account that can sign in and access the organization whose work you want to use.
  • Permission in Hidesc to access the requested records and perform the requested actions.
  • Your company must have API access enabled when subscription checks apply. If Hidesc reports that the feature is not included in your plan, ask your administrator or Hidesc support to check API access.

Use the Hidesc account you normally use for work. A Claude account alone does not grant access to Hidesc. If you need an account or an invitation, contact your Hidesc administrator or contact our team.

Connect in Claude

  1. Open Connectors. In Claude, go to Customize → Connectors. Some versions place Connectors under Settings.
  2. Add a custom connector. Choose Add, then Add custom connector. Enter Hidesc as the name and https://mcp.hidesc.com/mcp as the remote server URL.
  3. Continue with OAuth. Review the authentication Claude detects. Hidesc publishes OAuth discovery and supports automatic client registration. If Claude offers an OAuth client choice, use Register automatically. You do not need to paste your Hidesc password or a bearer token into the connector configuration.
  4. Sign in and connect. On the Hidesc connection page, enter your Hidesc email or username and password, then select Sign in and connect. This connects your current Hidesc company. If prompted, enter the verification code from your email or authenticator app.
  5. Return to Claude. After sign-in or verification, you should return automatically. If that does not happen, select Continue to your MCP client on the success page.
  6. Enable Hidesc in a conversation. Open a chat, select the + menu, then Connectors, and enable Hidesc. Ask Claude: “What tools are available from my Hidesc connector?”
Team and Enterprise accounts: An organization owner or authorized administrator may need to add the connector first. Each member then connects their own Hidesc account.

Claude’s menus can change. See Anthropic’s custom connector setup guide for current interface instructions.

Tools & example prompts

Hidesc provides the eight tools below. Read tools find records and their IDs; write tools create tasks, update task fields, or change task status. Delete operations are not exposed.

ToolPermissionPurpose & inputs
search_taskstasks:read

Search and filter tasks in your connected company.

No required inputs. Optional: search, projectId, workspaceId, statusName, assigneeId, contactId, parentId, priority, and pagination.

get_tasktasks:read

Retrieve the current details of one task.

Required: taskId (exact numeric Hidesc task ID).

create_tasktasks:write

Create a task using the fields required by its Hidesc template.

Required: name (1–500 characters). Additional fields may be required by the selected template. Resolve project, workspace, template, assignee, contact, and status IDs before creating.

update_tasktasks:write

Update task fields other than status. Read the task first and change only the requested fields.

Required: taskId, plus the fields to change. Supported fields include name, description, assigneeId, projectId, workspaceId, milestoneId, parentId, contactId, priority, dates, time, expectedHours, labels, taskType, verification, visibility, and custom fields.

update_task_statustasks:write

Move a task to a specific status item.

Required: taskId and statusId. Optional: failedReason, progressStatus. Confirm the task and exact target status ID first.

search_projectsprojects:read

Find projects and their IDs.

No required inputs. Optional: search, workspaceId, and pagination.

search_contactscontacts:read

Find contacts or clients and their IDs.

No required inputs. Optional: search and pagination.

list_team_membersusers:read

Find team members for task assignment.

No required inputs. Optional: search and pagination. Use assigneeId exactly as returned.

Input formats and task fields
  • Search/list tools accept search, page (default 1), limit (default 20, maximum 100), sort, and order (asc or desc; default desc).
  • IDs are positive integers or strings containing only digits. Use the returned numeric assigneeId directly; do not combine it with a company ID.
  • Task dates use Unix epoch milliseconds. startTime and endTime use milliseconds since local midnight, from 0 to 86,399,999. Tell Claude your intended date, time, and time zone.
  • Create accepts description, projectId, workspaceId, milestoneId, templateId, assigneeId, statusId, parentId, contactId, priority, startDate, dueDate, startTime, endTime, hasTime, expectedHours, labels, taskType, verifyingUsers, visibleUsers, isVerificationRequired, and customFields. An optional idempotencyKey is a stable UUID for retrying the same create request.
  • Update accepts the same task fields except templateId, statusId, and idempotencyKey. Use update_task_status for status changes. The connector has no dedicated template, workspace, or status lookup tool; supply those IDs from Hidesc if the available read results do not include them.

Try these prompts

search_tasks

“Search Hidesc for tasks in the Client Onboarding project and summarize their current status.”

get_task

“Find the task named Prepare monthly report, then show its details. Ask me to choose if several tasks match.”

create_task

“Prepare a task called Review client documents in the Client Onboarding project. Ask me for any required template fields and confirm the details before creating it.”

update_task

“Find Prepare monthly report and change only its description to Include the November totals. Show me the exact task and proposed change first.”

update_task_status

“Show the current status of Prepare monthly report. Before changing it, ask me to confirm the task and the target Hidesc status ID.”

search_projects

“Find the Hidesc project called Client Onboarding and show its ID.”

search_contacts

“Find the contact named Alex in Hidesc. If there are several matches, ask me which one I mean.”

list_team_members

“Find the Hidesc team member named Priya and show the assigneeId so I can confirm the right person.”

Include the project or task name and any relevant dates. If several records match, ask Claude to confirm the correct record. Review the proposed changes before approving a write action.

Permissions & access

The connection uses your signed-in Hidesc user and current company. The backend checks that your user is active and still belongs to that company. Your Hidesc permissions, company API-access entitlement, and the OAuth scope required by each tool apply to requests.

  • Use an account with access appropriate to the work you want Claude to perform.
  • If Hidesc denies a request, check the account, organization, role, and permissions rather than sharing another person’s credentials.
  • Disable tools you do not need in the current conversation. Only approve changes you understand.
  • To stop using the connection, disconnect or remove Hidesc from Claude’s Connectors settings. Contact Hidesc support if you also need help revoking the underlying authorization.

Hidesc supports OAuth token revocation. When an MCP client revokes an access or refresh token, Hidesc invalidates the associated family of tokens. Removing a connector in Claude and server-side revocation are separate actions; contact support if you need confirmation that the authorization has been revoked. Disconnecting does not delete tasks or undo changes already made.

Information returned by the connector becomes available in your Claude conversation. See the Hidesc Privacy Policy and your Claude account’s data settings.

Troubleshooting

I cannot add a custom connector

Check your Claude account’s connector settings. On a managed account, ask your organization owner or administrator to enable or add Hidesc.

Connection or authorization fails

Use the complete HTTPS URL, including /mcp. Retry the Connect action and complete the Hidesc sign-in flow. If authentication options are shown, use OAuth with automatic client registration.

The endpoint shows 401 or “Missing Authorization header” in my browser

The MCP endpoint is an authenticated service, not a normal webpage. Add it as a Claude connector and complete sign-in; visiting it directly does not authenticate your connector.

Hidesc is connected but no tools are used

Enable Hidesc in the current conversation and ask Claude to list its available Hidesc tools. Check that the specific tool is enabled and review any approval request.

Records are missing or access is denied

Confirm you signed in with the intended Hidesc account and can access the record in Hidesc itself. Ask your administrator to review your organization access and role.

The feature is not included in my plan

Ask your Hidesc administrator to check the company’s API-access entitlement. Successful OAuth sign-in does not bypass the API feature check.

I cannot finish verification or return to Claude

Use the code from the email or authenticator app requested by Hidesc. On the sign-in success page, select Continue to your MCP client if the automatic return does not complete.

Task creation or a status change needs more information

Task templates may require additional fields. Provide exact IDs for the project, template, workspace, assignee, or status when requested. Use update_task_status for a status change, not update_task.

A previously working connection stops

Reconnect Hidesc and sign in again if prompted. If the issue continues, contact support with the time, error message, and request ID if one is shown.

Need help connecting?

Email info@hidesc.com with your Claude client, the step that failed, and the error message. Include a request ID if available. Do not send passwords, access tokens, or private task content.

Contact Hidesc