HitWit Contact support
HitWit documentation

HitWit MCP connector

Bring your organization’s approved product, technical, sales, and partner knowledge into Claude.

Last updated · Remote MCP · OAuth sign-in required

Overview

The HitWit connector lets Claude search approved source material, request answers, retrieve supporting references, and suggest relevant next steps in your HitWit portal. It is designed for sales teams, sales engineers, and partners who already use HitWit.

Use it to research product capabilities, prepare for customer meetings, draft follow-up emails, or answer RFP and security questionnaire items. Answers depend on the content your organization has published and your current access.

A connector URL selects an organization; it does not grant access. You must sign in with an eligible HitWit account. The connector checks your organization membership and account permissions.

Before you connect

  • A Claude account that supports remote MCP connectors and any approval required by your Claude workspace administrator.
  • An existing HitWit account with access to the organization you want to connect.
  • The AI assistant connector enabled for that organization by a HitWit administrator.
  • Access to an active, indexed knowledge base for knowledge searches and answers.

Obtain your organization’s exact connector URL and any required OAuth client configuration from your administrator. Connecting does not create an account or add you to an organization.

Connect to Claude

There are two ways to connect: use your organization’s listing after it is approved in the Claude directory, or add a custom connector manually.

Use your organization’s approved listing if published for your org

This method is available once your organization’s connector submission has been approved and its listing is available in the Claude directory.

  1. Open Claude’s Connectors settings and browse the connector directory.
  2. Find the connector published for your organization and choose Connect. Use the listing name provided by your administrator.
  3. Continue to login.hitwit.ai, complete sign-in with your HitWit account, and return to Claude.
  4. Enable the connector in your chat and try one of the example prompts below.

The listing supplies the organization’s connector URL and OAuth client configuration. You do not need to enter them manually.

Method 2: Add a custom connector manually

You can add the connector yourself using the URL and OAuth client configuration supplied by your administrator. This method does not require an approved directory listing.

  1. Open Claude’s Connectors settings and choose the option to add a custom connector.
  2. Enter a name such as HitWit and use the connector URL below with your organization’s name.
  3. Choose Sign in now if Claude asks how authentication should work.
  4. If OAuth client settings are requested, choose Use your own OAuth client and enter the client ID supplied by your administrator. Leave the client secret blank for the currently configured public-client integration.
  5. Continue to login.hitwit.ai, complete sign-in with your HitWit account, and return to Claude.
  6. Enable the connector in your chat and try one of the example prompts below.

Your organization’s connector URL

https://mcp.hitwit.ai/mcp?org=<org>

Replace <org> with your organization’s name, for example hitwit. Organization names are case-sensitive.

Available Claude settings and custom connector access can vary by account and workspace. Obtain any approval required by your Claude workspace administrator.

Organization access

Sign in with a HitWit account that belongs to the organization in your connector URL. The connector checks your current membership and permissions on requests.

To review your connection context from Claude, ask:

Show my current HitWit organization and connection context.

If your access has changed, contact your administrator and reconnect as needed.

Available tools

Tools exposed by the HitWit MCP connector
ToolPurpose
pingCheck an authenticated connection. Returns pong.
get_account_contextShow your current connection context and available account contexts.
select_account_contextSave an eligible account context for subsequent requests.
search_knowledgeRetrieve approved source passages for a question or topic. Returns a response_id for follow-up tools.
get_answerGenerate an answer from approved knowledge. Supports brief or full detail, an optional purpose, and language.
get_answersAnswer up to 10 independent questions in one request. Each question has its own result status.
get_referencesRetrieve references relevant to an earlier result and the final answer supplied by Claude. Source links may require portal access.
suggest_actionsSuggest relevant, enabled portal features with short-lived sign-in links. Availability depends on organization settings and permissions.

Knowledge results can report that an answer was not found in approved content. Batch results can also report an error or timeout for an individual question. Review important answers against their supporting sources.

The connector does not automatically register deals, complete training, submit demo pitches, or run sales simulations. Suggested links open portal workflows for you to review and use. Portal sign-in links expire after five minutes; request a new suggestion if one expires.

Example prompts

Research a product

Use HitWit’s approved knowledge to explain [product]’s main capabilities and target users. Include supporting references and flag anything the sources do not answer.

Prepare a questionnaire

Answer these questions from our approved HitWit content: [question 1], [question 2], [question 3]. Keep each answer separate and identify any gaps.

Draft a customer follow-up

Draft a concise follow-up email about [product] for a [customer role]. Use approved claims, include relevant references, and suggest an available portal next step if useful.

Check the active organization

Which organization is HitWit using for this chat?

Replace bracketed text with the details of your task. Send only the information needed to answer the question.

Data and permissions

Claude sends the selected tool’s arguments to HitWit with an OAuth access token. HitWit uses the authenticated identity, organization, and permissions to authorize the request. The connector returns authorized account information, approved knowledge, answers, references, or portal links to Claude.

  • Connection preferences: context-selection tools can save the connection context used by subsequent requests.
  • Knowledge activity: HitWit records knowledge-tool questions, their user and account context, result status, and generated answers where applicable. Authorized organization administrators can review tool-call activity.
  • Follow-up content: when Claude calls the reference or suggested-action tools, the final answer passed to those tools is stored with the related response. Temporary response records used by follow-up tools expire after 24 hours. They include the question, retrieved references, and supplied final answer. This expiry is not a retention promise for all activity or operational records.
  • Source documents: references follow existing knowledge and portal permissions. A link does not make a private source publicly accessible.
  • Portal links: short-lived sign-in links are intended for the connected user. Treat them as private and do not forward them.

The integration has read and write capabilities for account preferences and service records. A tool marked as read-only can still create operational or query activity records.

Disconnect the connector in Claude to stop using it there. To remove organization access, contact your administrator. Signing out of the HitWit website is separate from disconnecting an OAuth connector.

See the HitWit Privacy Policy and your organization’s terms for data handling. Contact help@hitwit.ai with retention, deletion, or privacy questions. Claude’s handling of data is also governed by your Anthropic account and workspace settings.

Troubleshooting

Claude cannot check or connect to the server

Confirm the full URL, including the intended org parameter. Ask your administrator to check connector availability and OAuth discovery. Retry after any service incident. A reachable health endpoint alone does not verify sign-in or access to knowledge.

Sign-in fails or Claude asks to reconnect

Check that the OAuth client configuration belongs to this organization and environment, then reconnect. Your administrator may need to verify application access, callback configuration, or refresh-token settings. Do not put an access token or client secret in the connector URL.

Access denied or connector disabled

Verify your membership in the selected organization and that its administrator has enabled the AI assistant connector. A valid login alone does not grant organization access. Reconnect after an administrator changes OAuth permissions.

Your organization access has changed

Ask your administrator to review your current membership and permissions. Reconnect after access is restored or updated.

No approved answer, or an expected document is absent

Make the question specific. Confirm that the content is published, indexed, and accessible to your HitWit account. The connector cannot answer from documents you do not have permission to access.

A reference or next-step link does not open

Source links may require portal sign-in. For expired next-step links, request a new suggestion. If a response_id is unknown or expired, ask the original knowledge question again. No suggested actions may mean the feature or portal sign-in links are disabled for your connector.

Technical reference

The server uses stateless MCP Streamable HTTP with JSON responses. MCP protocol operations require a bearer access token. Health and HTTP OAuth discovery are publicly accessible.

SettingProduction value
HitWit connector URLhttps://mcp.hitwit.ai/mcp?org=hitwit
Canonical OAuth resource / audiencehttps://mcp.hitwit.ai/mcp
Authorization server issuerhttps://login.hitwit.ai/
Protected resource metadataOrganization-specific discovery document
Public health checkGET /mcp/health

Use /mcp?org=<organization-name> to select an organization. The OAuth audience remains the canonical /mcp URL. Required organization scopes are advertised by discovery; administrators must grant the client the relevant permissions.

Development and test clients should use the environment-specific URL provided by their administrator. Test and production access tokens have different API audiences.

Support

Email help@hitwit.ai with the organization name, environment, approximate time and time zone, and the error message or reference ID. Include a screenshot if useful.

Do not send passwords, OAuth authorization codes, access or refresh tokens, client secrets, or private portal sign-in links.