Connect an AI assistant to QuickStart

To connect an AI client to QuickStart, enable the QuickStart MCP server. The preferred setup method is to use the ChatGPT plugin or Claude connector from the agent stores. You can also configure a compatible MCP client with the Streamable HTTP endpoint in Manual configuration. Use OAuth when the client supports QuickStart’s OAuth flow; a personal access token is an alternative. Sign in to your account at QuickStart.

Before you begin

Enable the MCP server

  1. Sign in to your account at QuickStart.
  2. Open Menu > Administration. On the Administration page, select QuickStart settings.
  3. Select General.
  4. In the MCP Server section, select MCP Server Enabled.

Configure an AI client

Agent plugins

The preferred way to connect to the QuickStart MCP server is to use an integration from an agent store:

Manual configuration

To configure a compatible MCP client manually, use the following connection settings:

Enter the following URL in the AI client’s server configuration, not in your browser’s address bar:

https://my.quickstartapi.netsuite.com/mcp

For personal access token authentication, add the HTTP header Authorization: Bearer <PERSONAL_ACCESS_TOKEN>. Replace <PERSONAL_ACCESS_TOKEN> with the personal access token you generated. For instructions, see Create a personal access token.

Authorize an OAuth connection

When a compatible AI client starts an OAuth connection, sign in to QuickStart if prompted. QuickStart opens Grant application name access? in the browser.

  1. Verify that you recognize and trust the application and that the displayed QuickStart company ID is correct.
  2. Optionally enter a Registration name that helps you recognize the connection later.

  3. Select an available access level:

    • Read-only access lets the application view data within your user’s QuickStart permissions. This is selected initially.
    • Read and write access appears when the client registration permits it and lets the application view and modify data within your user’s QuickStart permissions.
  4. When Access duration (days) is displayed, enter a whole number from 1 through 90 days. The default is 30 days. This field appears for clients that support refresh tokens.
  5. Review Before you connect. Use only trusted clients, other connected MCP servers, and data sources. Content can contain prompt-injection instructions that influence the client to take unintended actions or disclose information. Configure the client to require your review before it changes or shares data. These precautions reduce risk but do not eliminate it.
  6. Review Third-party connection and AI terms, including the Oracle Terms of Use and Oracle’s Privacy Policy.
  7. Select Allow to continue or Deny access to reject the connection.

QuickStart returns the authorization result to the application. You need permission to access the OAuth registrations list and use its action; only the user who authorized a connection can revoke its grant. Sign in as that user and open Menu > Administration > QuickStart settings > OAuth client registrations. Open the connection’s row action menu and select Revoke when it is no longer needed. Revocation stops that connection’s access tokens and refresh tokens from providing access.

Create a personal access token

  1. Open Menu > Administration. On the Administration page, select QuickStart settings.
  2. Select Personal access tokens.
  3. Select Create personal access token.
  4. Review the security warning.
  5. In Name, enter a descriptive name that identifies the AI client.
  6. Review Expiration date. The default expiration date is 30 days after the token is created.
  7. Review Modification scope. Keep the default read-only scope unless the AI client must modify QuickStart data and you are authorized to grant that access.
  8. Select Create.
  9. In the confirmation dialog, select Copy token, and then store the token securely. The token is displayed only once.

Replace an expired or revoked personal access token

An AI client cannot authenticate with an expired or revoked personal access token. If your client uses a personal access token that is no longer valid, create a replacement and update the client’s configuration. This procedure applies to personal access token connections, not OAuth connections.

  1. Follow Create a personal access token to create and securely copy a replacement. Grant only the access the client needs.
  2. In your AI client’s configuration, replace the old token with the new token. Follow the instructions in Manual configuration. Do not paste the token into a chat message.
  3. Reload or restart the client as required for it to use the updated configuration.
  4. Request a read-only operation, such as listing the available QuickStart reports, to check the connection without changing business data.

The replacement token authenticates requests within its own permissions and expiration date. Replacing the client configuration does not reactivate the old token.

MCP server capabilities

A connected AI assistant can help you find QuickStart pages, read supported records and attachments, and run reports. With read and write access, it can also change supported records, update preferences, and send email. Available actions depend on your QuickStart permissions and the record’s state; connecting an assistant does not give it additional permissions.

Ask your AI client which operations it supports. Review proposed changes and outgoing messages before approving them. For financial actions, keep an authorized accounting professional responsible for checking results and approving changes, as described in Responsible use.

Technical reference for MCP clients

The tool names and request details below are for configuring or troubleshooting an MCP client. You do not need to enter these tool calls to follow the connection steps above.

With a read-only credential, the MCP server offers the following tools:

With a read-write credential, the MCP server also offers the following tools:

The exposed records include banking and reconciliation, accounting, sales and receivables, purchasing and payables, inventory and fulfillment, customer and vendor, product and service, subscription, status, and supporting reference records. To retrieve the exact current record type IDs, call get_record_model without recordType. Call it again with an exact record type ID before using another record tool so that the AI client can use the available fields, sublists, actions, and transforms correctly. Available actions and transforms depend on the record type and the specific record’s state. Retrieve the model for the record instead of assuming that a static action or transform is currently available. Purchasing and payables support additional transformations among purchase orders, recurring purchase orders, vendor bills, recurring vendor bills, vendor prepayments, vendor payments, vendor credits, and payment applications when the source record is eligible.

Use navigation_targets to find accessible QuickStart destinations and follow the links it returns rather than constructing a route. The exposed record model also includes supported custom fields. Generic transaction records can be read when available, but a record type’s presence in read results does not grant write access. Some additional record types support deletion; check the model and the current record’s available actions and permissions before requesting a change.

list_records returns an offset page. Set limit to an integer from 1 through 50; the default is 20. When the response contains nextOffset, pass that value as offset in the next call. Continue until nextOffset is null.

Use read_record_sublist for paged reads of a declared sublist. When a returned sublist descriptor includes a nested sublist, copy its sublistId and parentPath into another read_record_sublist request instead of expecting all nested lines in the parent record response. This also applies to exposed tax detail lines.

Use discover_preferences to identify the supported preference keys and value requirements, then use read_preferences to read a supported preference. A client with read and write access can use set_preferences. Company preference reads and updates require administrator access, and user preferences apply only to the authenticated user. MCP preference updates do not use the Ask Oracle chat approval flow, so configure the client to require your review before it changes a preference.

For a supported workflow that applies existing transactions, call get_record_apply_candidates before executing the transform. Use the candidate keys returned for that workflow instead of constructing them. A successful transform returns targetRecordType and targetId; call read_record with those values when the AI client needs the saved record contents. Native permissions and record lifecycle restrictions still apply.

For attachment sublists, call get_record_model and confirm that the record type has fileAttachable=true. Use upload_temporary_file to upload a file of up to 10 MB and receive a temporary contentHandle. Then use set_record_attachment with append to attach it to a record. To replace, delete, or update an existing attachment’s description, first call list_record_attachments and use the returned persistent lineId. The list also returns a download URL when the attachment content is available; open it in an authenticated QuickStart session. Use the attachment list’s pagination parameters when a record has more attachments than one response returns. Uploading a temporary file does not attach it to a record, and attachment mutations are not safely retryable.

The model can also expose attachmentFields, such as a product or service image, even when fileAttachable is false. Use the advertised fieldId for upload preparation, listing, and attachment changes; do not supply a sublist lineId for a body field. Append requires an empty field, while replacing or deleting content requires an occupied field. Respect the field’s allowed file extensions.

Use copy_record only for record types whose model supports copying. It creates a new record using QuickStart’s copy rules and the supported overrides; it does not edit the source. Review the source and proposed new values before approving a copy.

dismiss_notification can dismiss only the signed-in user’s eligible notifications. Use IDs returned by notifications, and review the target notifications before changing their state. For supported record types, get_record_model describes email actions and read_record shows which are currently available. A read and write connection can use send_record_email for an available action. Review recipients, subject, message, and attachments before sending because email has external effects and submitting it twice can send two messages.

Report catalog and run results include a browser-openable QuickStart URL. The URL uses the normal browser sign-in and report permission checks and does not contain the MCP credential. Configured report URLs preserve the temporary report state returned by the report tools.

Responsible use

Do not use AI-assisted QuickStart workflows as the sole basis for high-impact accounting decisions or financial actions, including posting or modifying transactions, approving payments or refunds, reconciling accounts, or changing customer, vendor, banking, or general ledger data. Keep an authorized accounting professional responsible for reviewing outputs and approving any action before it is performed. Verify AI-generated results against the underlying records and applicable accounting policies.

Use extra care when connecting an AI client to QuickStart and other services at the same time. Content from connected services, such as email, might be untrusted and contain prompt-injection instructions intended to influence the AI client. Treat that content as data instead of instructions, review proposed QuickStart actions before approval, and avoid granting unnecessary access or allowing financial actions to run automatically.

Important limitations

The published Claude QuickStart connector uses the connector workflow above. For other clients, use the applicable client instructions rather than assuming the same setup controls are available. Personal access token authentication remains available whenever the MCP server is enabled for the company. OAuth registration accepts supported local loopback callbacks and approved HTTPS callbacks for hosted clients.

OAuth access tokens last one hour. A client that supports refresh tokens can renew access until the approved access duration ends; renewal does not extend that end date. A connection without refresh support ends when its access token expires.

An application’s client ID identifies it; it does not give it permanent access to your data. You must sign in and approve each connection. Each approval has its own access level and duration. Revoking one connection does not revoke other connections you approved for the same application.

If QuickStart reports that a client registration is invalid or expired, restart the connection from the client. If the client keeps reusing the rejected registration, contact the integration’s support team rather than repeatedly granting access.

If an authorization callback is lost or its code expires, restart authorization from the client. To change the access level or approved duration for a connection, revoke that connection’s grant and authorize it again.

Learn more